From ba5b984528b6c500aed063af7f43ea24fa394f4e Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Wed, 27 Sep 2017 18:44:07 -0700 Subject: fixes #85 Protocols need to set msg pipe We looked at other options, but this is the least intrusive, even though it means that the protocols have to set it up. The reason is that transports have different methods of receiving messages, and there is no framework code between the transport and the protocol. --- src/protocol/pipeline/pull.c | 1 + 1 file changed, 1 insertion(+) (limited to 'src/protocol/pipeline/pull.c') diff --git a/src/protocol/pipeline/pull.c b/src/protocol/pipeline/pull.c index ba828763..80db2425 100644 --- a/src/protocol/pipeline/pull.c +++ b/src/protocol/pipeline/pull.c @@ -125,6 +125,7 @@ pull_recv_cb(void *arg) // Got a message... start the put to send it up to the application. msg = nni_aio_get_msg(aio); + nni_msg_set_pipe(msg, nni_pipe_id(p->pipe)); nni_aio_set_msg(aio, NULL); pull_putq(p, msg); } -- cgit v1.2.3-70-g09d2