From: Christian Brauner <brauner@kernel.org>
To: Yihuan Pan <xun794@gmail.com>, hch@lst.de
Cc: Christian Brauner <brauner@kernel.org>,
vgoyal@redhat.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] init: remove unused names parameter in split_fs_names()
Date: Mon, 5 Jun 2023 10:48:42 +0200 [thread overview]
Message-ID: <20230605-reckt-schob-73f835ae0cec@brauner> (raw)
In-Reply-To: <4lsiigvaw4lxcs37rlhgepv77xyxym6krkqcpc3xfncnswok3y@b67z3b44orar>
On Sat, 20 May 2023 15:23:32 +0800, Yihuan Pan wrote:
> The split_fs_names() function takes a names parameter, but the function
actually uses the root_fs_names global variable instead. This names parameter
is not used in the function, so it can be safely removed.
>
> This change does not affect the functionality of split_fs_names() or any
other part of the kernel.
>
>
I fixed up the commit message as requested by Christoph.
---
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.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] init: remove unused names parameter in split_fs_names()
https://git.kernel.org/vfs/vfs/c/7f1d63536bee
prev parent reply other threads:[~2023-06-05 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 7:23 [PATCH] init: remove unused names parameter in split_fs_names() Yihuan Pan
2023-05-20 7:34 ` Christoph Hellwig
2023-05-25 9:27 ` Christoph Hellwig
2023-06-05 8:48 ` 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=20230605-reckt-schob-73f835ae0cec@brauner \
--to=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xun794@gmail.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;
as well as URLs for NNTP newsgroup(s).