From: Jay Winston <jaybenjaminwinston@gmail.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jay Winston <jaybenjaminwinston@gmail.com>
Subject: [PATCH] fs/namei: fix kernel-doc markup for dentry_create
Date: Sun, 18 Jan 2026 13:04:01 +0200 [thread overview]
Message-ID: <20260118110401.2651-1-jaybenjaminwinston@gmail.com> (raw)
O_ is interpreted as a broken hyperlink target. Escape _ with a backslash.
The asterisk in "struct file *" is interpreted as an opening emphasis
string that never closes. Replace double quotes with rST backticks.
Change "a ERR_PTR" to "an ERR_PTR".
Signed-off-by: Jay Winston <jaybenjaminwinston@gmail.com>
---
fs/namei.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index b19890758646..f511288af463 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -4975,7 +4975,7 @@ EXPORT_SYMBOL(start_creating_user_path);
/**
* dentry_create - Create and open a file
* @path: path to create
- * @flags: O_ flags
+ * @flags: O\_ flags
* @mode: mode bits for new file
* @cred: credentials to use
*
@@ -4986,7 +4986,7 @@ EXPORT_SYMBOL(start_creating_user_path);
* the new file is to be created. The parent directory and the
* negative dentry must reside on the same filesystem instance.
*
- * On success, returns a "struct file *". Otherwise a ERR_PTR
+ * On success, returns a ``struct file *``. Otherwise an ERR_PTR
* is returned.
*/
struct file *dentry_create(struct path *path, int flags, umode_t mode,
--
2.46.4
next reply other threads:[~2026-01-18 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 11:04 Jay Winston [this message]
2026-01-19 8:47 ` [PATCH] fs/namei: fix kernel-doc markup for dentry_create Jan Kara
2026-01-20 13:54 ` Christian Brauner
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=20260118110401.2651-1-jaybenjaminwinston@gmail.com \
--to=jaybenjaminwinston@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--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