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] f2fs: allocate node blocks for atomic write block replacement
Date: Mon, 24 Apr 2023 18:10:19 +0000 [thread overview]
Message-ID: <168235981943.17900.16631584887911592592.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424154440.23279-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 24 Apr 2023 08:44:40 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> When a node block is missing for atomic write block replacement, we need
> to allocate it in advance of the replacement.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: allocate node blocks for atomic write block replacement
https://git.kernel.org/jaegeuk/f2fs/c/994b442b66a4
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
WARNING: multiple messages have this Message-ID (diff)
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: allocate node blocks for atomic write block replacement
Date: Mon, 24 Apr 2023 18:10:19 +0000 [thread overview]
Message-ID: <168235981943.17900.16631584887911592592.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230424154440.23279-1-daeho43@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 24 Apr 2023 08:44:40 -0700 you wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> When a node block is missing for atomic write block replacement, we need
> to allocate it in advance of the replacement.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: allocate node blocks for atomic write block replacement
https://git.kernel.org/jaegeuk/f2fs/c/994b442b66a4
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:[~2023-04-24 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:44 [f2fs-dev] [PATCH] f2fs: allocate node blocks for atomic write block replacement Daeho Jeong
2023-04-24 15:44 ` Daeho Jeong
2023-04-24 15:47 ` [f2fs-dev] " Chao Yu
2023-04-24 15:47 ` Chao Yu
2023-04-24 18:10 ` patchwork-bot+f2fs [this message]
2023-04-24 18:10 ` patchwork-bot+f2fs
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 17:42 Daeho Jeong
2023-04-21 2:25 ` Chao Yu
2023-04-21 2:25 ` 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=168235981943.17900.16631584887911592592.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.