From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hch@lst.de, josef@toxicpanda.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 0/2] Move fscrypt keyring destruction to after ->put_super
Date: Tue, 16 Jan 2024 19:02:18 +0000 [thread overview]
Message-ID: <170543173883.30188.3991145453418147928.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231227171429.9223-1-ebiggers@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers <ebiggers@google.com>:
On Wed, 27 Dec 2023 11:14:27 -0600 you wrote:
> This series moves the fscrypt keyring destruction to after ->put_super,
> as this will be needed by the btrfs fscrypt support. To make this
> possible, it also changes f2fs to release its block devices after
> generic_shutdown_super() rather than before.
>
> This supersedes "[PATCH] fscrypt: move the call to
> fscrypt_destroy_keyring() into ->put_super()"
> (https://lore.kernel.org/linux-fscrypt/20231206001325.13676-1-ebiggers@kernel.org/T/#u)
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: move release of block devices to after kill_block_super()
https://git.kernel.org/jaegeuk/f2fs/c/275dca4630c1
- [f2fs-dev,v2,2/2] fs: move fscrypt keyring destruction to after ->put_super
https://git.kernel.org/jaegeuk/f2fs/c/2a0e85719892
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-01-16 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 17:14 [PATCH v2 0/2] Move fscrypt keyring destruction to after ->put_super Eric Biggers
2023-12-27 17:14 ` [PATCH v2 1/2] f2fs: move release of block devices to after kill_block_super() Eric Biggers
2023-12-28 1:09 ` [f2fs-dev] " Chao Yu
2023-12-27 17:14 ` [PATCH v2 2/2] fs: move fscrypt keyring destruction to after ->put_super Eric Biggers
2024-01-16 19:02 ` 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=170543173883.30188.3991145453418147928.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@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 read-only IMAP folder(s) and NNTP newsgroup(s).