linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaskaran Singh <jaskaransingh7654321@gmail.com>
To: corbet@lwn.net
Cc: raven@themaw.net, akpm@linux-foundation.org,
	jaskaransingh7654321@gmail.com, mchehab+samsung@kernel.org,
	neilb@suse.com, christian@brauner.io, mszeredi@redhat.com,
	ebiggers@google.com, tobin@kernel.org, stefanha@redhat.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	skhan@linuxfoundation.org
Subject: [PATCH v2 2/3] docs: filesystems: Update code snippets in autofs.rst
Date: Sun, 17 Nov 2019 22:54:35 +0530	[thread overview]
Message-ID: <20191117172436.8831-3-jaskaransingh7654321@gmail.com> (raw)
In-Reply-To: <20191117172436.8831-1-jaskaransingh7654321@gmail.com>

Some of the struct definitions now have an autofs packet header.
Reflect these changes by adding a definition of this header and
place it wherever suitable.

Signed-off-by: Jaskaran Singh <jaskaransingh7654321@gmail.com>
---
 Documentation/filesystems/autofs.rst | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/Documentation/filesystems/autofs.rst b/Documentation/filesystems/autofs.rst
index 6702a5f61f50..2f704e9c5dc0 100644
--- a/Documentation/filesystems/autofs.rst
+++ b/Documentation/filesystems/autofs.rst
@@ -322,8 +322,7 @@ notification messages to this pipe for the daemon to respond to.
 For version 5, the format of the message is::
 
 	struct autofs_v5_packet {
-		int proto_version;		/* Protocol version */
-		int type;			/* Type of packet */
+		struct autofs_packet_hdr hdr;
 		autofs_wqt_t wait_queue_token;
 		__u32 dev;
 		__u64 ino;
@@ -335,6 +334,13 @@ For version 5, the format of the message is::
 		char name[NAME_MAX+1];
         };
 
+And the format of the header is::
+
+	struct autofs_packet_hdr {
+		int proto_version;		/* Protocol version */
+		int type;			/* Type of packet */
+	};
+
 where the type is one of ::
 
 	autofs_ptype_missing_indirect
@@ -395,8 +401,7 @@ The available ioctl commands are:
 	anything suitable to expire.  A pointer to a packet::
 
 		struct autofs_packet_expire_multi {
-			int proto_version;		/* Protocol version */
-			int type;			/* Type of packet */
+			struct autofs_packet_hdr hdr;
 			autofs_wqt_t wait_queue_token;
 			int len;
 			char name[NAME_MAX+1];
-- 
2.21.0


  parent reply	other threads:[~2019-11-17 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 17:24 [PATCH v2 0/3] docs: filesystems: convert autofs.txt to reST Jaskaran Singh
2019-11-17 17:24 ` [PATCH v2 1/3] " Jaskaran Singh
2019-11-17 17:24 ` Jaskaran Singh [this message]
2019-11-17 17:24 ` [PATCH v2 3/3] docs: filesystems: Add mount map description in Content Jaskaran Singh
2019-11-17 23:50   ` Ian Kent
2019-11-18 19:21 ` [PATCH v2 0/3] docs: filesystems: convert autofs.txt to reST Jonathan Corbet

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=20191117172436.8831-3-jaskaransingh7654321@gmail.com \
    --to=jaskaransingh7654321@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=christian@brauner.io \
    --cc=corbet@lwn.net \
    --cc=ebiggers@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=neilb@suse.com \
    --cc=raven@themaw.net \
    --cc=skhan@linuxfoundation.org \
    --cc=stefanha@redhat.com \
    --cc=tobin@kernel.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;
as well as URLs for NNTP newsgroup(s).