From: patchwork-bot+f2fs@kernel.org
To: Wu Bo <bo.wu@vivo.com>
Cc: liaoyuanhong@vivo.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, wubo.oduw@gmail.com,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix block migration when section is not aligned to pow2
Date: Sat, 11 May 2024 00:50:34 +0000 [thread overview]
Message-ID: <171538863413.11229.14009197979317413967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240429035142.706356-1-bo.wu@vivo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 28 Apr 2024 21:51:42 -0600 you wrote:
> As for zoned-UFS, f2fs section size is forced to zone size. And zone
> size may not aligned to pow2.
>
> Fixes: 859fca6b706e ("f2fs: swap: support migrating swapfile in aligned write mode")
> Signed-off-by: Liao Yuanhong <liaoyuanhong@vivo.com>
> Signed-off-by: Wu Bo <bo.wu@vivo.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix block migration when section is not aligned to pow2
https://git.kernel.org/jaegeuk/f2fs/c/aa4074e8fec4
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:[~2024-05-11 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 3:51 [f2fs-dev] [PATCH v2] f2fs: fix block migration when section is not aligned to pow2 Wu Bo via Linux-f2fs-devel
2024-04-30 1:03 ` Chao Yu
2024-05-11 0:50 ` 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=171538863413.11229.14009197979317413967.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=bo.wu@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=liaoyuanhong@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wubo.oduw@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).