From: patchwork-bot+f2fs@kernel.org
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
daehojeong@google.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: prevent atomic file from being dirtied before commit
Date: Fri, 30 Aug 2024 20:51:52 +0000 [thread overview]
Message-ID: <172505111299.2712133.3150061801664189477.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240826202352.2150294-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 26 Aug 2024 13:23:52 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Keep atomic file clean while updating and make it dirtied during commit
> in order to avoid unnecessary and excessive inode updates in the previous
> fix.
>
> Fixes: 4bf78322346f ("f2fs: mark inode dirty for FI_ATOMIC_COMMITTED flag")
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: prevent atomic file from being dirtied before commit
https://git.kernel.org/jaegeuk/f2fs/c/a433a8f0eb31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-30 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 20:23 [PATCH] f2fs: prevent atomic file from being dirtied before commit Daeho Jeong
2024-08-30 20:51 ` patchwork-bot+f2fs [this message]
2024-09-02 10:08 ` [f2fs-dev] " Chao Yu
2024-09-03 17:07 ` Daeho Jeong
2024-09-04 2:26 ` Chao Yu
2024-09-04 2:52 ` Daeho Jeong
2024-09-04 3:35 ` Chao Yu
2024-09-04 14:56 ` Daeho Jeong
2024-09-04 14:58 ` Daeho Jeong
2024-09-05 1:06 ` Chao Yu
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=172505111299.2712133.3150061801664189477.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