From: patchwork-bot+f2fs@kernel.org
To: Yangtao Li <frank.li@vivo.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4 1/3] f2fs: fix to set ipu policy
Date: Tue, 07 Feb 2023 19:00:17 +0000 [thread overview]
Message-ID: <167579641783.24576.11656544535078514322.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230206144310.2344-1-frank.li@vivo.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 6 Feb 2023 22:43:08 +0800 you wrote:
> For LFS mode, it should update outplace and no need inplace update.
> When using LFS mode for small-volume devices, IPU will not be used,
> and the OPU writing method is actually used, but F2FS_IPU_FORCE can
> be read from the ipu_policy node, which is different from the actual
> situation. And remount to lfs mode should be disallowed when
> f2fs ipu is enabled, let's fix it.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4,1/3] f2fs: fix to set ipu policy
(no matching commit)
- [f2fs-dev,v4,2/3] f2fs: add missing description for ipu_policy node
https://git.kernel.org/jaegeuk/f2fs/c/9e615dbba41e
- [f2fs-dev,v4,3/3] f2fs: introduce ipu_mode sysfs node
(no matching commit)
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:[~2023-02-07 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:43 Yangtao Li
2023-02-06 14:43 ` [PATCH v4 2/3] f2fs: add missing description for ipu_policy node Yangtao Li
2023-02-06 14:43 ` [PATCH v4 3/3] f2fs: introduce ipu_mode sysfs node Yangtao Li
2023-02-07 18:50 ` Jaegeuk Kim
2023-02-07 13:24 ` [PATCH v4 1/3] f2fs: fix to set ipu policy Chao Yu
2023-02-07 18:46 ` Jaegeuk Kim
2023-02-07 19:00 ` 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=167579641783.24576.11656544535078514322.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--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®