From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/3] remove shared memory structures
Date: Tue, 21 Mar 2023 16:40:18 +0000 [thread overview]
Message-ID: <167941681881.25004.14989603719608389854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313201216.924234-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 13 Mar 2023 13:12:13 -0700 you wrote:
> This series removes the use of rb_entry based on memory alignment which doesn't
> look like a right design when considering various architectures/compilers.
>
> v2 from v1:
> - adjusted Eric's review
> - refactored gc.c further to clean up
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: factor out victim_entry usage from general rb_tree use
https://git.kernel.org/jaegeuk/f2fs/c/e433c7887585
- [f2fs-dev,2/3] f2fs: factor out discard_cmd usage from general rb_tree use
https://git.kernel.org/jaegeuk/f2fs/c/7e9775a516ff
- [f2fs-dev,3/3] f2fs: remove entire rb_entry sharing
https://git.kernel.org/jaegeuk/f2fs/c/6b40bc364c10
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: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/3] remove shared memory structures
Date: Tue, 21 Mar 2023 16:40:18 +0000 [thread overview]
Message-ID: <167941681881.25004.14989603719608389854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313201216.924234-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 13 Mar 2023 13:12:13 -0700 you wrote:
> This series removes the use of rb_entry based on memory alignment which doesn't
> look like a right design when considering various architectures/compilers.
>
> v2 from v1:
> - adjusted Eric's review
> - refactored gc.c further to clean up
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: factor out victim_entry usage from general rb_tree use
https://git.kernel.org/jaegeuk/f2fs/c/e433c7887585
- [f2fs-dev,2/3] f2fs: factor out discard_cmd usage from general rb_tree use
https://git.kernel.org/jaegeuk/f2fs/c/7e9775a516ff
- [f2fs-dev,3/3] f2fs: remove entire rb_entry sharing
https://git.kernel.org/jaegeuk/f2fs/c/6b40bc364c10
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-03-21 16:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:12 [f2fs-dev] [PATCH 0/3] remove shared memory structures Jaegeuk Kim
2023-03-13 20:12 ` Jaegeuk Kim
2023-03-13 20:12 ` [f2fs-dev] [PATCH 1/3] f2fs: factor out victim_entry usage from general rb_tree use Jaegeuk Kim
2023-03-13 20:12 ` Jaegeuk Kim
2023-03-23 14:22 ` [f2fs-dev] " Chao Yu
2023-03-23 14:22 ` Chao Yu
2023-03-13 20:12 ` [f2fs-dev] [PATCH 2/3] f2fs: factor out discard_cmd " Jaegeuk Kim
2023-03-13 20:12 ` Jaegeuk Kim
2023-03-23 14:31 ` [f2fs-dev] " Chao Yu
2023-03-23 14:31 ` Chao Yu
2023-03-24 16:57 ` [f2fs-dev] [PATCH 2/3 v2] " Jaegeuk Kim
2023-03-24 16:57 ` Jaegeuk Kim
2023-03-26 3:50 ` [f2fs-dev] " Chao Yu
2023-03-26 3:50 ` Chao Yu
2023-03-13 20:12 ` [f2fs-dev] [PATCH 3/3] f2fs: remove entire rb_entry sharing Jaegeuk Kim
2023-03-13 20:12 ` Jaegeuk Kim
2023-03-23 14:32 ` [f2fs-dev] " Chao Yu
2023-03-23 14:32 ` Chao Yu
2023-03-21 16:40 ` patchwork-bot+f2fs [this message]
2023-03-21 16:40 ` [f2fs-dev] [PATCH 0/3] remove shared memory structures 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=167941681881.25004.14989603719608389854.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@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.