From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/4] fs: remove fsparam_path / fs_param_is_path
Date: Fri, 20 Feb 2026 16:24:02 +0100 [thread overview]
Message-ID: <20260220152402.GB14300@lst.de> (raw)
In-Reply-To: <20260219160428.GQ6467@frogsfrogsfrogs>
On Thu, Feb 19, 2026 at 08:04:28AM -0800, Darrick J. Wong wrote:
> > diff --git a/Documentation/filesystems/mount_api.rst b/Documentation/filesystems/mount_api.rst
> > index b4a0f23914a6..e8b94357b4df 100644
> > --- a/Documentation/filesystems/mount_api.rst
> > +++ b/Documentation/filesystems/mount_api.rst
> > @@ -648,7 +648,6 @@ The members are as follows:
> > fs_param_is_enum Enum value name result->uint_32
> > fs_param_is_string Arbitrary string param->string
> > fs_param_is_blockdev Blockdev path * Needs lookup
>
> Unrelated: should xfs be using fsparam_bdev for its logdev/rtdev mount
> options?
Not sure what the point is in having separate string helpers with meaning,
but maybe I'm missing something/
> Or, more crazily, should it grow logfd/rtfd options that use fsparam_fd?
What would the use case be for that?
next prev parent reply other threads:[~2026-02-20 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 6:50 remove or unexport unused fs_conext infrastructure Christoph Hellwig
2026-02-19 6:50 ` [PATCH 1/4] fs: mark bool_names static Christoph Hellwig
2026-02-19 6:50 ` [PATCH 2/4] fs: remove fsparam_blob / fs_param_is_blob Christoph Hellwig
2026-02-19 6:50 ` [PATCH 3/4] fs: remove fsparam_path / fs_param_is_path Christoph Hellwig
2026-02-19 16:04 ` Darrick J. Wong
2026-02-20 15:24 ` Christoph Hellwig [this message]
2026-02-20 18:21 ` Darrick J. Wong
2026-02-19 6:50 ` [PATCH 4/4] fs: unexport fs_context_for_reconfigure Christoph Hellwig
2026-02-19 11:45 ` remove or unexport unused fs_conext infrastructure Jan Kara
2026-02-19 13:35 ` 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=20260220152402.GB14300@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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