From: patchwork-bot+f2fs@kernel.org
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
jaegeuk@kernel.org, daehojeong@google.com
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: separate f2fs_gc_range() to use GC for a range
Date: Wed, 21 Feb 2024 18:10:30 +0000 [thread overview]
Message-ID: <170853903091.7043.10526328421276609740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213173812.1432663-1-daeho43@gmail.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 13 Feb 2024 09:38:11 -0800 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Make f2fs_gc_range() an extenal function to use it for GC for a range.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: separate f2fs_gc_range() to use GC for a range
https://git.kernel.org/jaegeuk/f2fs/c/50581e3bda8f
- [f2fs-dev,v3,2/2] f2fs: support file pinning for zoned devices
https://git.kernel.org/jaegeuk/f2fs/c/2fded30d8dce
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-02-21 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 17:38 [PATCH v3 1/2] f2fs: separate f2fs_gc_range() to use GC for a range Daeho Jeong
2024-02-13 17:38 ` [PATCH v3 2/2] f2fs: support file pinning for zoned devices Daeho Jeong
2024-02-23 3:23 ` [f2fs-dev] " Chao Yu
2024-02-23 3:43 ` Chao Yu
2024-02-23 3:52 ` Chao Yu
2024-02-23 17:31 ` Jaegeuk Kim
2024-02-25 6:30 ` Chao Yu
2024-02-20 8:37 ` [f2fs-dev] [PATCH v3 1/2] f2fs: separate f2fs_gc_range() to use GC for a range Chao Yu
2024-02-21 18:10 ` 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=170853903091.7043.10526328421276609740.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--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