diff options
| author | Djalal Harouni <tixxdz@opendz.org> | 2015-01-24 22:37:47 +0100 |
|---|---|---|
| committer | Djalal Harouni <tixxdz@opendz.org> | 2015-01-24 22:37:47 +0100 |
| commit | b2e6e351c25922ef75758819900afc4b2505e875 (patch) | |
| tree | b961aae47d71e77e7a0528a98cba753bec387081 | |
| parent | e7ddfb1da4ad1edd71a937893adf10e8d60c7ab8 (diff) | |
| download | kdbus-bus-b2e6e351c25922ef75758819900afc4b2505e875.tar.gz kdbus-bus-b2e6e351c25922ef75758819900afc4b2505e875.tar.bz2 kdbus-bus-b2e6e351c25922ef75758819900afc4b2505e875.zip | |
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 <tixxdz@opendz.org>
| -rw-r--r-- | kdbus.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/kdbus.txt b/kdbus.txt index c149ccc8aa8..2ddc9894051 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 |