From: Eric Biggers <ebiggers@kernel.org>
To: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Cc: tytso@mit.edu, jaegeuk@kernel.org, linux-fscrypt@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v1 00/10] fscrypt: rearrangements preliminary to extent encryption
Date: Mon, 10 Apr 2023 19:19:28 +0000 [thread overview]
Message-ID: <ZDRhQGYfOsJjzbjx@gmail.com> (raw)
In-Reply-To: <cover.1681116739.git.sweettea-kernel@dorminy.me>
On Mon, Apr 10, 2023 at 06:16:21AM -0400, Sweet Tea Dorminy wrote:
> Patchset should apply cleanly to fscrypt/for-next
It doesn't apply. What is the base commit?
- Eric
next prev parent reply other threads:[~2023-04-10 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 10:16 [PATCH v1 00/10] fscrypt: rearrangements preliminary to extent encryption Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 01/10] fscrypt: split and rename setup_file_encryption_key() Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 02/10] fscrypt: split and rename setup_per_mode_enc_key() Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 03/10] fscrypt: move dirhash key setup away from IO key setup Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 04/10] fscrypt: reduce special-casing of IV_INO_LBLK_32 Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 05/10] fscrypt: make infos have a pointer to prepared keys Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 06/10] fscrypt: move all the shared mode key setup deeper Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 07/10] fscrypt: make ci->ci_direct_key a bool not a pointer Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 08/10] fscrypt: make prepared keys record their type Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 09/10] fscrypt: explicitly track prepared parts of key Sweet Tea Dorminy
2023-04-10 10:16 ` [PATCH v1 10/10] fscrypt: split key alloc and preparation Sweet Tea Dorminy
2023-04-10 19:19 ` Eric Biggers [this message]
2023-04-10 19:40 ` [PATCH v1 00/10] fscrypt: rearrangements preliminary to extent encryption Sweet Tea Dorminy
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=ZDRhQGYfOsJjzbjx@gmail.com \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.