From: patchwork-bot+f2fs@kernel.org
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 1/2] f2fs: prevent atomic write on pinned file
Date: Wed, 13 Mar 2024 01:30:29 +0000 [thread overview]
Message-ID: <171029342984.17296.1929429193688050018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240311235921.1832684-1-daeho43@gmail.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 11 Mar 2024 16:59:19 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Since atomic write way was changed to out-place-update, we should
> prevent it on pinned files.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: prevent atomic write on pinned file
https://git.kernel.org/jaegeuk/f2fs/c/c644af133283
- [f2fs-dev,2/2] f2fs: prevent writing without fallocate() for pinned files
(no matching commit)
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-03-13 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 23:59 [f2fs-dev] [PATCH 1/2] f2fs: prevent atomic write on pinned file Daeho Jeong
2024-03-11 23:59 ` [f2fs-dev] [PATCH 2/2] f2fs: prevent writing without fallocate() for pinned files Daeho Jeong
2024-03-12 1:50 ` Chao Yu
2024-03-12 1:43 ` [f2fs-dev] [PATCH 1/2] f2fs: prevent atomic write on pinned file Chao Yu
2024-03-13 1:30 ` 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=171029342984.17296.1929429193688050018.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).