linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Eric Sandeen <sandeen@redhat.com>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org, linux-fsdevel@vger.kernel.org,
	jaegeuk@kernel.org, lihongbo22@huawei.com
Subject: Re: [PATCH 1/7] f2fs: Add fs parameter specifications for mount options
Date: Wed, 7 May 2025 17:54:18 +0800	[thread overview]
Message-ID: <04099a70-c0b0-4bd5-92be-07694d9a1741@kernel.org> (raw)
In-Reply-To: <20250420154647.1233033-2-sandeen@redhat.com>

On 4/20/25 23:25, Eric Sandeen wrote:
> From: Hongbo Li <lihongbo22@huawei.com>
> 
> Use an array of `fs_parameter_spec` called f2fs_param_specs to
> hold the mount option specifications for the new mount api.
> 
> Add constant_table structures for several options to facilitate
> parsing.
> 
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
> [sandeen: forward port, minor fixes and updates, more fsparam_enum]
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2025-05-07  9:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-20 15:24 [PATCH 0/7 V2] f2fs: new mount API conversion Eric Sandeen
2025-04-20 15:25 ` [PATCH 1/7] f2fs: Add fs parameter specifications for mount options Eric Sandeen
2025-05-07  9:54   ` Chao Yu [this message]
2025-04-20 15:25 ` [PATCH 2/7] f2fs: move the option parser into handle_mount_opt Eric Sandeen
2025-05-07 11:26   ` Chao Yu
2025-05-07 12:31     ` Eric Sandeen
2025-05-07 15:02       ` Jaegeuk Kim
2025-05-08  3:29         ` Chao Yu
2025-05-08  3:28       ` Chao Yu
2025-04-20 15:25 ` [PATCH 3/7] f2fs: Allow sbi to be NULL in f2fs_printk Eric Sandeen
2025-05-07 11:29   ` Chao Yu
2025-04-20 15:25 ` [PATCH 4/7] f2fs: Add f2fs_fs_context to record the mount options Eric Sandeen
2025-04-20 15:25 ` [PATCH 5/7] f2fs: separate the options parsing and options checking Eric Sandeen
2025-04-21 16:34   ` kernel test robot
2025-04-21 17:37   ` kernel test robot
2025-04-21 17:37   ` kernel test robot
2025-04-20 15:25 ` [PATCH 6/7] f2fs: introduce fs_context_operation structure Eric Sandeen
2025-04-20 15:25 ` [PATCH 7/7] f2fs: switch to the new mount api Eric Sandeen
2025-04-22  2:39 ` [PATCH 0/7 V2] f2fs: new mount API conversion Eric Sandeen
2025-07-11 16:30 ` [f2fs-dev] " patchwork-bot+f2fs

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=04099a70-c0b0-4bd5-92be-07694d9a1741@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.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).