From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: brauner@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
lczerner@redhat.com, linux-fsdevel@vger.kernel.org,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion
Date: Fri, 11 Jul 2025 16:30:09 +0000 [thread overview]
Message-ID: <175225140924.2328592.1750911075772737839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240814023912.3959299-1-lihongbo22@huawei.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 14 Aug 2024 10:39:03 +0800 you wrote:
> Since many filesystems have done the new mount API conversion,
> we introduce the new mount API conversion in f2fs.
>
> The series can be applied on top of the current mainline tree
> and the work is based on the patches from Lukas Czerner (has
> done this in ext4[1]). His patch give me a lot of ideas.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/9] f2fs: Add fs parameter specifications for mount options
(no matching commit)
- [f2fs-dev,2/9] f2fs: move the option parser into handle_mount_opt
(no matching commit)
- [f2fs-dev,3/9] f2fs: move option validation into a separate helper
(no matching commit)
- [f2fs-dev,4/9] f2fs: Allow sbi to be NULL in f2fs_printk
(no matching commit)
- [f2fs-dev,5/9] f2fs: Add f2fs_fs_context to record the mount options
(no matching commit)
- [f2fs-dev,6/9] f2fs: separate the options parsing and options checking
(no matching commit)
- [f2fs-dev,7/9] f2fs: introduce fs_context_operation structure
https://git.kernel.org/jaegeuk/f2fs/c/54e12a4e0209
- [f2fs-dev,8/9] f2fs: switch to the new mount api
(no matching commit)
- [f2fs-dev,9/9] f2fs: remove unused structure and functions
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-07-11 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 2:39 [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 1/9] f2fs: Add fs parameter specifications for mount options Hongbo Li via Linux-f2fs-devel
2024-08-30 21:00 ` Eric Sandeen
2024-08-14 2:39 ` [f2fs-dev] [PATCH 2/9] f2fs: move the option parser into handle_mount_opt Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 3/9] f2fs: move option validation into a separate helper Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 4/9] f2fs: Allow sbi to be NULL in f2fs_printk Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 5/9] f2fs: Add f2fs_fs_context to record the mount options Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 6/9] f2fs: separate the options parsing and options checking Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 7/9] f2fs: introduce fs_context_operation structure Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 8/9] f2fs: switch to the new mount api Hongbo Li via Linux-f2fs-devel
2024-08-14 2:39 ` [f2fs-dev] [PATCH 9/9] f2fs: remove unused structure and functions Hongbo Li via Linux-f2fs-devel
2024-08-27 11:47 ` [f2fs-dev] [PATCH 0/9] f2fs: new mount API conversion Hongbo Li via Linux-f2fs-devel
2024-08-30 17:07 ` Eric Sandeen
2024-08-31 1:45 ` Hongbo Li via Linux-f2fs-devel
2024-09-11 2:04 ` Hongbo Li via Linux-f2fs-devel
2024-09-12 1:11 ` Chao Yu via Linux-f2fs-devel
2024-09-12 1:49 ` Hongbo Li via Linux-f2fs-devel
2025-07-11 16:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 9:12 Hongbo Li via Linux-f2fs-devel
2024-08-12 10:43 ` Hongbo Li via Linux-f2fs-devel
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=175225140924.2328592.1750911075772737839.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=brauner@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lczerner@redhat.com \
--cc=lihongbo22@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
/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).