From: Al Viro <viro@zeniv.linux.org.uk>
To: Zizhi Wo <wozizhi@huaweicloud.com>
Cc: Jan Kara <jack@suse.cz>,
brauner@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, yangerkun@huawei.com
Subject: Re: [PATCH] fs: Rename the parameter of mnt_get_write_access()
Date: Sat, 17 May 2025 00:57:39 +0100 [thread overview]
Message-ID: <20250516235739.GV2023217@ZenIV> (raw)
In-Reply-To: <b3d6db6f-61d8-498a-b90c-0716a64f7528@huaweicloud.com>
On Sat, May 17, 2025 at 07:54:55AM +0800, Zizhi Wo wrote:
>
>
> 在 2025/5/16 18:31, Jan Kara 写道:
> > On Fri 16-05-25 11:21:47, Zizhi Wo wrote:
> > > From: Zizhi Wo <wozizhi@huawei.com>
> > >
> > > Rename the parameter in mnt_get_write_access() from "m" to "mnt" for
> > > consistency between declaration and implementation.
> > >
> > > Signed-off-by: Zizhi Wo <wozizhi@huawei.com>
> >
> > I'm sorry but this is just a pointless churn. I agree the declaration and
> > implementation should better be consistent (although in this particular
> > case it isn't too worrying) but it's much easier (and with much lower
> > chance to cause conflicts) to just fixup the declaration.
> >
> > Honza
>
> Yes, I had considered simply fixing the declaration earlier. However, in
> the include/linux/mount.h file, similar functions like
> "mnt_put_write_access" use "mnt" as the parameter name rather than "m",
> just like "mnt_get_write_access". So I chose to modify the function
> implementation directly, although this resulted in a larger amount of
> changes. So as you can see, for simplicity, I will directly update the
> parameter name in the function declaration in the second version.
FWIW, "mnt for vfsmount, m for mount" is an informal convention in that
area, so I'd say go for it if there had been any change in the function
in question. Same as with coding style, really...
next prev parent reply other threads:[~2025-05-16 23:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 3:21 [PATCH] fs: Rename the parameter of mnt_get_write_access() Zizhi Wo
2025-05-16 10:31 ` Jan Kara
2025-05-16 23:54 ` Zizhi Wo
2025-05-16 23:57 ` Al Viro [this message]
2025-05-17 0:09 ` Zizhi Wo
2025-05-22 1:01 ` Zizhi Wo
2025-05-22 7:41 ` Amir Goldstein
2025-05-22 8:02 ` Zizhi Wo
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=20250516235739.GV2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wozizhi@huaweicloud.com \
--cc=yangerkun@huawei.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 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.