From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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: introduce is_{meta,node}_folio
Date: Wed, 28 May 2025 16:20:27 +0000 [thread overview]
Message-ID: <174844922750.2455931.7003358490084665923.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250523073304.1454247-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 23 May 2025 15:33:03 +0800 you wrote:
> Just cleanup, no changes.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/checkpoint.c | 4 ++--
> fs/f2fs/data.c | 2 +-
> fs/f2fs/f2fs.h | 13 +++++++++++--
> fs/f2fs/gc.c | 2 +-
> fs/f2fs/node.c | 18 +++++++++---------
> 5 files changed, 24 insertions(+), 15 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: introduce is_{meta,node}_folio
https://git.kernel.org/jaegeuk/f2fs/c/019a8912425e
- [f2fs-dev,2/2] f2fs: clean up to check bi_status w/ BLK_STS_OK
https://git.kernel.org/jaegeuk/f2fs/c/68e7f31eecf1
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
prev parent reply other threads:[~2025-05-28 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 7:33 [f2fs-dev] [PATCH 1/2] f2fs: introduce is_{meta,node}_folio Chao Yu via Linux-f2fs-devel
2025-05-23 7:33 ` [f2fs-dev] [PATCH 2/2] f2fs: clean up to check bi_status w/ BLK_STS_OK Chao Yu via Linux-f2fs-devel
2025-05-28 16:20 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=174844922750.2455931.7003358490084665923.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@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).