From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range()
Date: Tue, 31 Jan 2023 19:10:20 +0000 [thread overview]
Message-ID: <167519222011.20142.17605283450543529387.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131144701.34418-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 31 Jan 2023 22:46:59 +0800 you wrote:
> No logic change, just avoid goto statement.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/extent_cache.c | 66 ++++++++++++++++++++----------------------
> 1 file changed, 31 insertions(+), 35 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: clean up __update_extent_tree_range()
(no matching commit)
- [f2fs-dev,2/3] f2fs: fix to update age extent correctly during truncation
https://git.kernel.org/jaegeuk/f2fs/c/334ce4a79c9e
- [f2fs-dev,3/3] f2fs: fix to update age extent in f2fs_do_zero_range()
https://git.kernel.org/jaegeuk/f2fs/c/de6b3a5e09b2
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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range()
Date: Tue, 31 Jan 2023 19:10:20 +0000 [thread overview]
Message-ID: <167519222011.20142.17605283450543529387.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131144701.34418-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 31 Jan 2023 22:46:59 +0800 you wrote:
> No logic change, just avoid goto statement.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/extent_cache.c | 66 ++++++++++++++++++++----------------------
> 1 file changed, 31 insertions(+), 35 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: clean up __update_extent_tree_range()
(no matching commit)
- [f2fs-dev,2/3] f2fs: fix to update age extent correctly during truncation
https://git.kernel.org/jaegeuk/f2fs/c/334ce4a79c9e
- [f2fs-dev,3/3] f2fs: fix to update age extent in f2fs_do_zero_range()
https://git.kernel.org/jaegeuk/f2fs/c/de6b3a5e09b2
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-01-31 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:46 [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range() Chao Yu
2023-01-31 14:46 ` Chao Yu
2023-01-31 14:47 ` [f2fs-dev] [PATCH 2/3] f2fs: fix to update age extent correctly during truncation Chao Yu
2023-01-31 14:47 ` Chao Yu
2023-01-31 14:47 ` [f2fs-dev] [PATCH 3/3] f2fs: fix to update age extent in f2fs_do_zero_range() Chao Yu
2023-01-31 14:47 ` Chao Yu
2023-01-31 18:56 ` [f2fs-dev] [PATCH 1/3] f2fs: clean up __update_extent_tree_range() Jaegeuk Kim
2023-01-31 18:56 ` Jaegeuk Kim
2023-02-01 8:53 ` [f2fs-dev] " Chao Yu
2023-02-01 8:53 ` Chao Yu
2023-02-06 3:41 ` [f2fs-dev] " Jaegeuk Kim
2023-02-06 3:41 ` Jaegeuk Kim
2023-02-07 12:33 ` [f2fs-dev] " Chao Yu
2023-02-07 12:33 ` Chao Yu
2023-01-31 19:10 ` patchwork-bot+f2fs [this message]
2023-01-31 19:10 ` [f2fs-dev] " patchwork-bot+f2fs
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=167519222011.20142.17605283450543529387.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=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 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.