From: Christian Brauner <brauner@kernel.org>
To: Jay Winston <jaybenjaminwinston@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH] fs/namei: fix kernel-doc markup for dentry_create
Date: Tue, 20 Jan 2026 14:54:16 +0100 [thread overview]
Message-ID: <20260120-stunk-rational-5065ba74bddd@brauner> (raw)
In-Reply-To: <20260118110401.2651-1-jaybenjaminwinston@gmail.com>
On Sun, 18 Jan 2026 13:04:01 +0200, Jay Winston wrote:
> 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".
>
> [...]
Applied to the vfs-6.20.atomic_open branch of the vfs/vfs.git tree.
Patches in the vfs-6.20.atomic_open branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.20.atomic_open
[1/1] fs/namei: fix kernel-doc markup for dentry_create
https://git.kernel.org/vfs/vfs/c/6ea258d1f689
prev parent reply other threads:[~2026-01-20 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 11:04 [PATCH] fs/namei: fix kernel-doc markup for dentry_create Jay Winston
2026-01-19 8:47 ` Jan Kara
2026-01-20 13:54 ` Christian Brauner [this message]
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=20260120-stunk-rational-5065ba74bddd@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jaybenjaminwinston@gmail.com \
--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