From: patchwork-bot+f2fs@kernel.org
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
adilger.kernel@dilger.ca, tytso@mit.edu, krisman@suse.de,
brauner@kernel.org, jack@suse.cz, ebiggers@google.com,
viro@zeniv.linux.org.uk, kernel@collabora.com
Subject: Re: [f2fs-dev] [PATCH v18 0/7] Case insensitive cleanup for ext4/f2fs
Date: Wed, 24 Jul 2024 02:16:46 +0000 [thread overview]
Message-ID: <172178740660.17759.10253649840019036127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240606073353.47130-1-eugen.hristev@collabora.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Thu, 6 Jun 2024 10:33:46 +0300 you wrote:
> Hello,
>
> I am trying to respin the series here :
> https://www.spinics.net/lists/linux-ext4/msg85081.html
>
> I resent some of the v9 patches and got some reviews from Gabriel,
> I did changes as requested and here is v18.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v18,1/7] ext4: Simplify the handling of cached casefolded names
https://git.kernel.org/jaegeuk/f2fs/c/f776f02a2c96
- [f2fs-dev,v18,2/7] f2fs: Simplify the handling of cached casefolded names
https://git.kernel.org/jaegeuk/f2fs/c/632f4054b229
- [f2fs-dev,v18,3/7] libfs: Introduce case-insensitive string comparison helper
https://git.kernel.org/jaegeuk/f2fs/c/6a79a4e187bd
- [f2fs-dev,v18,4/7] ext4: Reuse generic_ci_match for ci comparisons
https://git.kernel.org/jaegeuk/f2fs/c/d76b92f61f3b
- [f2fs-dev,v18,5/7] f2fs: Reuse generic_ci_match for ci comparisons
https://git.kernel.org/jaegeuk/f2fs/c/d66858eb0c72
- [f2fs-dev,v18,6/7] ext4: Move CONFIG_UNICODE defguards into the code flow
https://git.kernel.org/jaegeuk/f2fs/c/d98c822232f8
- [f2fs-dev,v18,7/7] f2fs: Move CONFIG_UNICODE defguards into the code flow
https://git.kernel.org/jaegeuk/f2fs/c/28add38d545f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-24 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 7:33 [PATCH v18 0/7] Case insensitive cleanup for ext4/f2fs Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 1/7] ext4: Simplify the handling of cached casefolded names Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 2/7] f2fs: " Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 3/7] libfs: Introduce case-insensitive string comparison helper Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 4/7] ext4: Reuse generic_ci_match for ci comparisons Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 5/7] f2fs: " Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 6/7] ext4: Move CONFIG_UNICODE defguards into the code flow Eugen Hristev
2024-06-06 7:33 ` [PATCH v18 7/7] f2fs: " Eugen Hristev
2024-06-06 21:50 ` [PATCH v18 0/7] Case insensitive cleanup for ext4/f2fs Gabriel Krisman Bertazi
2024-06-07 15:04 ` Christian Brauner
2024-06-07 15:03 ` Christian Brauner
2024-07-24 2:16 ` 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=172178740660.17759.10253649840019036127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=ebiggers@google.com \
--cc=eugen.hristev@collabora.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).