From: Christian Brauner <brauner@kernel.org>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: Eugen Hristev <eugen.hristev@collabora.com>,
Christian Brauner <christian@brauner.io>,
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, chao@kernel.org,
viro@zeniv.linux.org.uk, jack@suse.cz, ebiggers@google.com,
kernel@collabora.com
Subject: Re: [PATCH v18 0/7] Case insensitive cleanup for ext4/f2fs
Date: Fri, 7 Jun 2024 17:04:49 +0200 [thread overview]
Message-ID: <20240607-skaten-geophysik-685b6532b78e@brauner> (raw)
In-Reply-To: <87v82livv5.fsf@mailhost.krisman.be>
> Christian, can you please take a look? Eric has also been involved in
Thanks! Looks good to me. I've picked it up for testing in -next.
next prev parent reply other threads:[~2024-06-07 15:04 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 [this message]
2024-06-07 15:03 ` Christian Brauner
2024-07-24 2:16 ` [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=20240607-skaten-geophysik-685b6532b78e@brauner \
--to=brauner@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=chao@kernel.org \
--cc=christian@brauner.io \
--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).