From: Djalal Harouni Date: Sat, 24 Jan 2015 21:37:47 +0000 (+0100) Subject: doc: KDBUS_MSG_SYNC_REPLY was replaced by KDBUS_SEND_SYNC_REPLY X-Git-Tag: upstream/0.20150129.081441utc~25 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=b2e6e351c25922ef75758819900afc4b2505e875;p=platform%2Fcore%2Fsystem%2Fkdbus-bus.git doc: KDBUS_MSG_SYNC_REPLY was replaced by KDBUS_SEND_SYNC_REPLY There is no more KDBUS_MSG_SYNC_REPLY, it was replaced by KDBUS_SEND_SYNC_REPLY. This is only a documentation fix. Signed-off-by: Djalal Harouni --- diff --git a/kdbus.txt b/kdbus.txt index c149ccc..2ddc989 100644 --- a/kdbus.txt +++ b/kdbus.txt @@ -807,7 +807,7 @@ struct kdbus_cmd_send { non-blocking. However, as there are many use cases that need to wait for a remote peer to answer a method call, there's a way to send a message and wait for a reply in a synchronous fashion. This is what - the KDBUS_MSG_SYNC_REPLY controls. The KDBUS_CMD_SEND ioctl will block + the KDBUS_SEND_SYNC_REPLY controls. The KDBUS_CMD_SEND ioctl will block until the reply has arrived, the timeout limit is reached, in case the remote connection was shut down, or if interrupted by a signal before any reply; see signal(7). @@ -1990,7 +1990,7 @@ For KDBUS_CMD_SEND: sockets. Both are currently unsupported -EINVAL The submitted payload type is KDBUS_PAYLOAD_KERNEL, KDBUS_MSG_EXPECT_REPLY was set without timeout or cookie - values, KDBUS_MSG_SYNC_REPLY was set without + values, KDBUS_SEND_SYNC_REPLY was set without KDBUS_MSG_EXPECT_REPLY, an invalid item was supplied, src_id was non-zero and was different from the current connection's ID, a supplied memfd had a size of 0, a string was