linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Documentation: kdbus: Fix description of KDBUS_SEND_SYNC_REPLY flag
@ 2015-04-09 10:08 Sergei Zviagintsev
  2015-04-09 10:19 ` Daniel Mack
  2015-04-10 11:44 ` Greg Kroah-Hartman
  0 siblings, 2 replies; 3+ messages in thread
From: Sergei Zviagintsev @ 2015-04-09 10:08 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Daniel Mack, David Herrmann, Djalal Harouni
  Cc: Jonathan Corbet, linux-kernel, linux-doc, Sergei Zviagintsev

Signed-off-by: Sergei Zviagintsev <sergei@s15v.net>
---
 Documentation/kdbus/kdbus.message.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/kdbus/kdbus.message.xml b/Documentation/kdbus/kdbus.message.xml
index 061a407d50c7..0115d9d50db3 100644
--- a/Documentation/kdbus/kdbus.message.xml
+++ b/Documentation/kdbus/kdbus.message.xml
@@ -242,8 +242,8 @@ struct kdbus_cmd_send {
                   </citerefentry>.
 
                   The offset of the reply message in the sender's pool is stored
-                  in in <varname>offset_reply</varname> when the ioctl has
-                  returned without error. Hence, there is no need for another
+                  in <varname>reply</varname> when the ioctl has returned without
+                  error. Hence, there is no need for another
                   <constant>KDBUS_CMD_RECV</constant> ioctl or anything else to
                   receive the reply.
                 </para>
-- 
1.8.3.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-04-10 11:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-09 10:08 [PATCH] Documentation: kdbus: Fix description of KDBUS_SEND_SYNC_REPLY flag Sergei Zviagintsev
2015-04-09 10:19 ` Daniel Mack
2015-04-10 11:44 ` Greg Kroah-Hartman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).