From: Djalal Harouni Date: Sat, 24 Jan 2015 21:42:19 +0000 (+0100) Subject: doc: replace KDBUS_MSG_PAYLOAD_{VEC|MEMFD} with KDBUS_ITEM_PAYLOAD_{VEC|MEMFD} X-Git-Tag: upstream/0.20150129.081441utc~24 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=9ae48d07d35fc3df516fb65696fe3c4717cab8dc;p=platform%2Fcore%2Fsystem%2Fkdbus-bus.git doc: replace KDBUS_MSG_PAYLOAD_{VEC|MEMFD} with KDBUS_ITEM_PAYLOAD_{VEC|MEMFD} Replace KDBUS_MSG_PAYLOAD_VEC and KDBUS_MSG_PAYLOAD_MEMFD with KDBUS_ITEM_PAYLOAD_VEC and KDBUS_ITEM_PAYLOAD_MEMFD respectively. This is a documentation fix. Signed-off-by: Djalal Harouni --- diff --git a/kdbus.txt b/kdbus.txt index 2ddc989..33a8375 100644 --- a/kdbus.txt +++ b/kdbus.txt @@ -991,12 +991,12 @@ large enough to carry all backlog of data enqueued for the connection. The pool is internally backed by a shared memory file which can be mmap()ed by the receiver. -KDBUS_MSG_PAYLOAD_VEC: +KDBUS_ITEM_PAYLOAD_VEC: Messages are directly copied by the sending process into the receiver's pool. This way, two peers can exchange data by effectively doing a single-copy from one process to another; the kernel will not buffer the data anywhere else. -KDBUS_MSG_PAYLOAD_MEMFD: +KDBUS_ITEM_PAYLOAD_MEMFD: Messages can reference memfd files which contain the data. memfd files are tmpfs-backed files that allow sealing of the content of the file, which prevents all writable access to the file content. @@ -2003,7 +2003,7 @@ For KDBUS_CMD_SEND: is too big. -EEXIST Multiple KDBUS_ITEM_FDS, KDBUS_ITEM_BLOOM_FILTER or KDBUS_ITEM_DST_NAME items were supplied - -EBADF The supplied KDBUS_ITEM_FDS or KDBUS_MSG_PAYLOAD_MEMFD items + -EBADF The supplied KDBUS_ITEM_FDS or KDBUS_ITEM_PAYLOAD_MEMFD items contained an illegal file descriptor -EMEDIUMTYPE The supplied memfd is not a sealed kdbus memfd -EMFILE Too many file descriptors inside a KDBUS_ITEM_FDS