From: Alex Shi <alex.shi@linux.alibaba.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Joel Becker <jlbec@evilplan.org>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] configfs: fix kernel-doc markup issue
Date: Fri, 13 Nov 2020 16:58:13 +0800 [thread overview]
Message-ID: <1605257895-5536-4-git-send-email-alex.shi@linux.alibaba.com> (raw)
In-Reply-To: <1605257895-5536-1-git-send-email-alex.shi@linux.alibaba.com>
Add explanation for 'frag' parameter to avoid kernel-doc issue:
fs/configfs/dir.c:277: warning: Function parameter or member 'frag' not
described in 'configfs_create_dir'
Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Joel Becker <jlbec@evilplan.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org
---
fs/configfs/dir.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/configfs/dir.c b/fs/configfs/dir.c
index b0983e2a4e2c..b839dd1b459f 100644
--- a/fs/configfs/dir.c
+++ b/fs/configfs/dir.c
@@ -267,6 +267,7 @@ static void configfs_remove_dirent(struct dentry *dentry)
* configfs_create_dir - create a directory for an config_item.
* @item: config_itemwe're creating directory for.
* @dentry: config_item's dentry.
+ * @frag: config_item's fragment.
*
* Note: user-created entries won't be allowed under this new directory
* until it is validated by configfs_dir_set_ready()
--
2.29.GIT
next prev parent reply other threads:[~2020-11-13 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 8:58 [PATCH] PM / suspend: fix kernel-doc markup Alex Shi
2020-11-13 8:58 ` [PATCH] locking/rtmutex: add missed " Alex Shi
2021-01-12 13:28 ` Will Deacon
2021-01-27 19:31 ` [tip: locking/core] locking/rtmutex: Add missing " tip-bot2 for Alex Shi
2021-01-28 12:21 ` tip-bot2 for Alex Shi
2020-11-13 8:58 ` [PATCH] locking/rtmutex: remove useless parameter for rt_mutex_proxy_unlock Alex Shi
2021-01-12 13:31 ` Will Deacon
2020-11-13 8:58 ` Alex Shi [this message]
2020-11-14 9:26 ` [PATCH] configfs: fix kernel-doc markup issue Christoph Hellwig
2020-11-13 8:58 ` [PATCH] x86/PCI: fix a comments issue Alex Shi
2020-11-27 13:06 ` [tip: x86/cleanups] x86/PCI: Make a kernel-doc comment a normal one tip-bot2 for Alex Shi
2020-11-13 8:58 ` [PATCH] PKCS#7: drop function from kernel-doc pkcs7_validate_trust_one Alex Shi
2020-11-23 17:26 ` [PATCH] PM / suspend: fix kernel-doc markup Rafael J. Wysocki
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=1605257895-5536-4-git-send-email-alex.shi@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.