From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/8] f2fs: remove __add_sum_entry
Date: Tue, 31 Jan 2023 19:10:20 +0000 [thread overview]
Message-ID: <167519222001.20142.1808718951493834107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119063625.466485-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 19 Jan 2023 07:36:18 +0100 you wrote:
> This function just assigns a summary entry. This can be done entirely
> typesafe with an open code struct assignment that relies on array
> indexing.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/f2fs/segment.c | 23 ++---------------------
> 1 file changed, 2 insertions(+), 21 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/8] f2fs: remove __add_sum_entry
https://git.kernel.org/jaegeuk/f2fs/c/2163a691c5f3
- [f2fs-dev,2/8] f2fs: simplify do_checkpoint
https://git.kernel.org/jaegeuk/f2fs/c/bc6cc6f92b89
- [f2fs-dev,3/8] f2fs: add a f2fs_curseg_valid_blocks helper
https://git.kernel.org/jaegeuk/f2fs/c/0034f8954469
- [f2fs-dev,4/8] f2fs: factor the read/write tracing logic into a helper
(no matching commit)
- [f2fs-dev,5/8] f2fs: refactor __allocate_new_segment
https://git.kernel.org/jaegeuk/f2fs/c/53577f7c5b8b
- [f2fs-dev,6/8] f2fs: remove __allocate_new_section
https://git.kernel.org/jaegeuk/f2fs/c/b2164fbdb8f8
- [f2fs-dev,7/8] f2fs: refactor next blk selection
https://git.kernel.org/jaegeuk/f2fs/c/33234f9705d8
- [f2fs-dev,8/8] f2fs: remove __has_curseg_space
https://git.kernel.org/jaegeuk/f2fs/c/b8574d8c47eb
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
next prev parent reply other threads:[~2023-01-31 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 6:36 [f2fs-dev] misc f2fs cleanups Christoph Hellwig
2023-01-19 6:36 ` [f2fs-dev] [PATCH 1/8] f2fs: remove __add_sum_entry Christoph Hellwig
2023-01-29 10:29 ` Chao Yu
2023-01-31 19:10 ` patchwork-bot+f2fs [this message]
2023-01-19 6:36 ` [f2fs-dev] [PATCH 2/8] f2fs: simplify do_checkpoint Christoph Hellwig
2023-01-29 10:30 ` Chao Yu
2023-01-19 6:36 ` [f2fs-dev] [PATCH 3/8] f2fs: add a f2fs_curseg_valid_blocks helper Christoph Hellwig
2023-01-29 10:34 ` Chao Yu
2023-01-19 6:36 ` [f2fs-dev] [PATCH 4/8] f2fs: factor the read/write tracing logic into a helper Christoph Hellwig
2023-01-29 10:36 ` Chao Yu
2023-01-30 23:00 ` Jaegeuk Kim
2023-01-19 6:36 ` [f2fs-dev] [PATCH 5/8] f2fs: refactor __allocate_new_segment Christoph Hellwig
2023-01-29 10:39 ` Chao Yu
2023-01-19 6:36 ` [f2fs-dev] [PATCH 6/8] f2fs: remove __allocate_new_section Christoph Hellwig
2023-01-29 10:39 ` Chao Yu
2023-01-19 6:36 ` [f2fs-dev] [PATCH 7/8] f2fs: refactor next blk selection Christoph Hellwig
2023-01-29 12:20 ` Chao Yu
2023-01-19 6:36 ` [f2fs-dev] [PATCH 8/8] f2fs: remove __has_curseg_space Christoph Hellwig
2023-01-29 12:24 ` 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=167519222001.20142.1808718951493834107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.