From: Christian Brauner <brauner@kernel.org>
To: Yan Zhen <yanzhen@vivo.com>
Cc: Christian Brauner <brauner@kernel.org>,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, opensource.kernel@vivo.com,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v1] proc: Fix typo in the comment
Date: Mon, 9 Sep 2024 09:51:41 +0200 [thread overview]
Message-ID: <20240909-frieden-yacht-7b67be6a8a3c@brauner> (raw)
In-Reply-To: <20240909063353.2246419-1-yanzhen@vivo.com>
On Mon, 09 Sep 2024 14:33:53 +0800, Yan Zhen wrote:
> The deference here confuses me.
>
> Maybe here want to say that because show_fd_locks() does not dereference
> the files pointer, using the stale value of the files pointer is safe.
>
> Correctly spelled comments make it easier for the reader to understand
> the code.
>
> [...]
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc 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.misc
[1/1] proc: Fix typo in the comment
https://git.kernel.org/vfs/vfs/c/698e7d168054
prev parent reply other threads:[~2024-09-09 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 6:33 Yan Zhen
2024-09-09 7:51 ` 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=20240909-frieden-yacht-7b67be6a8a3c@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
--cc=yanzhen@vivo.com \
/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
all inboxes | Powered by JetHome®