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] fix per-block age-based extent_cache
Date: Tue, 03 Jan 2023 18:50:16 +0000 [thread overview]
Message-ID: <167277181645.18849.7061029698605018840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221217004659.2092427-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 16 Dec 2022 16:46:56 -0800 you wrote:
> Clean up and one bug fix.
>
> Jaegeuk Kim (3):
> f2fs: initialize extent_cache parameter
> f2fs: don't mix to use union values in extent_info
> f2fs: should use a temp extent_info for lookup
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: initialize extent_cache parameter
https://git.kernel.org/jaegeux/f2fs/c/fe59109ae5c0
- [f2fs-dev,2/3] f2fs: don't mix to use union values in extent_info
https://git.kernel.org/jaegeux/f2fs/c/ed2724765e58
- [f2fs-dev,3/3] f2fs: should use a temp extent_info for lookup
https://git.kernel.org/jaegeux/f2fs/c/22a341b43036
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
prev parent reply other threads:[~2023-01-03 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 0:46 [f2fs-dev] [PATCH 0/3] fix per-block age-based extent_cache Jaegeuk Kim
2022-12-17 0:46 ` [f2fs-dev] [PATCH 1/3] f2fs: initialize extent_cache parameter Jaegeuk Kim
2022-12-17 0:46 ` [f2fs-dev] [PATCH 2/3] f2fs: don't mix to use union values in extent_info Jaegeuk Kim
2022-12-17 0:46 ` [f2fs-dev] [PATCH 3/3] f2fs: should use a temp extent_info for lookup Jaegeuk Kim
2023-01-03 18:50 ` patchwork-bot+f2fs [this message]
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=167277181645.18849.7061029698605018840.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).