From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: allow F2FS_IPU_NOCACHE for pinned file
Date: Thu, 19 Sep 2024 09:24:42 +0800 [thread overview]
Message-ID: <a7ffb7d2-28e9-4cba-95ee-6a34acff973e@kernel.org> (raw)
In-Reply-To: <20240915032251.2300459-1-jaegeuk@kernel.org>
On 2024/9/15 11:22, Jaegeuk Kim via Linux-f2fs-devel wrote:
> This patch allows f2fs to submit bios of in-place writes on pinned file.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2024-09-19 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 3:22 [PATCH] f2fs: allow F2FS_IPU_NOCACHE for pinned file Jaegeuk Kim
2024-09-16 19:41 ` [f2fs-dev] " Daeho Jeong
2024-09-16 21:30 ` patchwork-bot+f2fs
2024-09-19 1:24 ` Chao Yu [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=a7ffb7d2-28e9-4cba-95ee-6a34acff973e@kernel.org \
--to=chao@kernel.org \
--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