From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Christoph Hellwig <hch@lst.de>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
"David P . Quigley" <dpquigl@tycho.nsa.gov>,
James Morris <jmorris@namei.org>
Subject: [PATCH -next] fs: libfs: fix kernel-doc for mnt_userns
Date: Mon, 15 Feb 2021 20:29:27 -0800 [thread overview]
Message-ID: <20210216042929.8931-2-rdunlap@infradead.org> (raw)
In-Reply-To: <20210216042929.8931-1-rdunlap@infradead.org>
Fix kernel-doc warning in libfs.c.
../fs/libfs.c:498: warning: Function parameter or member 'mnt_userns' not described in 'simple_setattr'
Fixes: 549c7297717c ("fs: make helpers idmap mount aware")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Cc: Christian Brauner <christian.brauner@ubuntu.com>
---
fs/libfs.c | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20210215.orig/fs/libfs.c
+++ linux-next-20210215/fs/libfs.c
@@ -481,6 +481,7 @@ EXPORT_SYMBOL(simple_rename);
/**
* simple_setattr - setattr for simple filesystem
+ * @mnt_userns: user namespace of the target mount
* @dentry: dentry
* @iattr: iattr structure
*
next prev parent reply other threads:[~2021-02-16 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 4:29 [PATCH -next] fs: fix new and older kernel-doc warnings in fs/ Randy Dunlap
2021-02-16 4:29 ` Randy Dunlap [this message]
2021-02-16 8:48 ` [PATCH -next] fs: libfs: fix kernel-doc for mnt_userns Christoph Hellwig
2021-02-16 9:41 ` Christian Brauner
2021-03-01 11:54 ` Christian Brauner
2021-02-16 4:29 ` [PATCH -next] fs: namei: fix kernel-doc for struct renamedata and more Randy Dunlap
2021-02-16 4:29 ` [PATCH -next] fs: xattr: fix kernel-doc for mnt_userns and vfs xattr helpers Randy Dunlap
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=20210216042929.8931-2-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=christian.brauner@ubuntu.com \
--cc=dhowells@redhat.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).