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/2] f2fs: rename page_count with cache_count
Date: Tue, 22 Sep 2026 15:30:13 +0000 [thread overview]
Message-ID: <179009101314.4140645.13210408538473891144.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260911232510.1816298-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 12 Sep 2026 07:25:09 +0800 you wrote:
> From: Jaegeuk Kim <jaegeuk@kernel.org>
>
> The count does not indicate the number of pages anymore.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/cache.c | 4 ++--
> fs/f2fs/checkpoint.c | 30 ++++++++++++-------------
> fs/f2fs/compress.c | 8 +++----
> fs/f2fs/data.c | 32 +++++++++++++--------------
> fs/f2fs/debug.c | 26 +++++++++++-----------
> fs/f2fs/f2fs.h | 41 ++++++++++++++++++----------------
> fs/f2fs/file.c | 14 ++++++------
> fs/f2fs/gc.c | 14 ++++++------
> fs/f2fs/node.c | 10 ++++-----
> fs/f2fs/segment.c | 10 ++++-----
> fs/f2fs/segment.h | 10 ++++-----
> fs/f2fs/super.c | 52 ++++++++++++++++++++++----------------------
> 12 files changed, 127 insertions(+), 124 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: rename page_count with cache_count
(no matching commit)
- [f2fs-dev,2/2] f2fs: rename nr_pages_to_skip with nr_caches_to_skip
https://git.kernel.org/jaegeuk/f2fs/c/a4b9fb9e6911
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:[~2026-09-22 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 23:25 Chao Yu
2026-09-11 23:25 ` [PATCH 2/2] f2fs: rename nr_pages_to_skip with nr_caches_to_skip Chao Yu
2026-09-22 15:30 ` 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=179009101314.4140645.13210408538473891144.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
all inboxes | Powered by JetHome®