From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: zone: introduce first_zoned_segno in f2fs_sb_info
Date: Mon, 28 Oct 2024 17:40:42 +0000 [thread overview]
Message-ID: <173013724273.126843.1612111639944304594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241018062638.2619214-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 18 Oct 2024 14:26:36 +0800 you wrote:
> first_zoned_segno() returns a fixed value, let's cache it in
> structure f2fs_sb_info to avoid redundant calculation.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/f2fs.h | 1 +
> fs/f2fs/segment.c | 4 ++--
> fs/f2fs/segment.h | 10 ----------
> fs/f2fs/super.c | 13 +++++++++++++
> 4 files changed, 16 insertions(+), 12 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: zone: introduce first_zoned_segno in f2fs_sb_info
https://git.kernel.org/jaegeuk/f2fs/c/08060c0b1414
- [f2fs-dev,2/3] f2fs: zone: allow IPU for regular file in regular block device
(no matching commit)
- [f2fs-dev,3/3] f2fs: support NOCoW flag
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-28 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 6:26 [PATCH 1/3] f2fs: zone: introduce first_zoned_segno in f2fs_sb_info Chao Yu
2024-10-18 6:26 ` [PATCH 2/3] f2fs: zone: allow IPU for regular file in regular block device Chao Yu
2024-10-21 23:18 ` Jaegeuk Kim
2024-10-22 1:58 ` Chao Yu
2024-10-18 6:26 ` [PATCH 3/3] f2fs: support NOCoW flag Chao Yu
2024-10-28 17:40 ` patchwork-bot+f2fs [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=173013724273.126843.1612111639944304594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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