mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergei Zviagintsev <sergei@s15v.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Mack <daniel@zonque.org>,
	David Herrmann <dh.herrmann@googlemail.com>,
	Djalal Harouni <tixxdz@opendz.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Sergei Zviagintsev <sergei@s15v.net>
Subject: [PATCH] Documentation: kdbus: Fix description of KDBUS_SEND_SYNC_REPLY flag
Date: Thu,  9 Apr 2015 13:08:05 +0300	[thread overview]
Message-ID: <1428574087-18502-2-git-send-email-sergei@s15v.net> (raw)

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


             reply	other threads:[~2015-04-09 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 10:08 Sergei Zviagintsev [this message]
2015-04-09 10:19 ` Daniel Mack
2015-04-10 11:44 ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1428574087-18502-2-git-send-email-sergei@s15v.net \
    --to=sergei@s15v.net \
    --cc=corbet@lwn.net \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tixxdz@opendz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®