From: patchwork-bot+f2fs@kernel.org
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: tytso@mit.edu, jaegeuk@kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel@collabora.com,
adilger.kernel@dilger.ca, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [RESEND PATCH v9 0/2] Minor cleanup for case insensitive path
Date: Wed, 24 Jul 2024 02:16:46 +0000 [thread overview]
Message-ID: <172178740664.17759.11130907548289451069.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240207064302.221060-1-eugen.hristev@collabora.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Wed, 7 Feb 2024 08:43:00 +0200 you wrote:
> Hello,
>
> I am trying to respin the series here :
> https://www.spinics.net/lists/linux-ext4/msg85081.html
>
> To make it easier to apply I split it into smaller chunks which address
> one single thing.
> This series will just convert to qstr the storage of the filename
> currently using fscrypt_str .
>
> [...]
Here is the summary with links:
- [f2fs-dev,RESEND,v9,1/2] ext4: Simplify the handling of cached insensitive names
https://git.kernel.org/jaegeuk/f2fs/c/f776f02a2c96
- [f2fs-dev,RESEND,v9,2/2] f2fs: Simplify the handling of cached insensitive names
(no matching commit)
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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 6:43 [RESEND PATCH v9 0/2] Minor cleanup for case insensitive path Eugen Hristev
2024-02-07 6:43 ` [RESEND PATCH v9 1/2] ext4: Simplify the handling of cached insensitive names Eugen Hristev
2024-02-07 6:43 ` [RESEND PATCH v9 2/2] f2fs: " Eugen Hristev
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=172178740664.17759.11130907548289451069.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=eugen.hristev@collabora.com \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).