From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Daeho Jeong <daeho43@gmail.com>
Cc: daehojeong@google.com, kernel-team@android.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v7] f2fs: support dynamic reserve/release for device aliasing
Date: Tue, 11 Aug 2026 04:30:09 +0000 [thread overview]
Message-ID: <178642260963.332426.908773733240280355.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806014813.1587003-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 5 Aug 2026 18:48:13 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> This patch adds a dynamic management feature to the existing device
> aliasing functionality. It allows users to dynamically reserve or
> release specific devices from the filesystem's free pool at runtime
> through new ioctls.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v7] f2fs: support dynamic reserve/release for device aliasing
https://git.kernel.org/jaegeuk/f2fs/c/eae3faf210bd
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:[~2026-08-11 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 1:48 [f2fs-dev] [PATCH v7] f2fs: support dynamic reserve/release for device aliasing Daeho Jeong
2026-08-06 2:43 ` Chao Yu via Linux-f2fs-devel
2026-08-11 4:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-08-20 20:30 ` Christophe JAILLET via Linux-f2fs-devel
2026-08-20 21:01 ` Daeho Jeong
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=178642260963.332426.908773733240280355.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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