From: Eric Biggers <ebiggers@kernel.org>
To: Daniel Rosenberg <drosen@google.com>
Cc: linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>,
kernel-team@android.com
Subject: Re: [PATCH v2 0/3] Fscrypt support for casefolded encryption
Date: Mon, 6 Jan 2020 19:26:59 -0800 [thread overview]
Message-ID: <20200107032659.GB705@sol.localdomain> (raw)
In-Reply-To: <20200107023323.38394-1-drosen@google.com>
On Mon, Jan 06, 2020 at 06:33:20PM -0800, Daniel Rosenberg wrote:
> These patches are to prepare fscrypt to support casefolding and
> encryption at the same time. Other patches will add those to the
> vfs, ext4 and f2fs. These patches are against fscrypt/master
>
> Daniel Rosenberg (3):
> fscrypt: Add siphash and hash key for policy v2
> fscrypt: Don't allow v1 policies with casefolding
> fscrypt: Change format of no-key token
>
I think you should send out the full series again so that people have the needed
context when reviewing it. It can still be on top of fscrypt.git#master if
that's easiest. We can consider taking these three patches for 5.6 before the
fs/ext4/ and fs/f2fs/ parts in order to help avoid merge conflicts between git
trees, but that doesn't mean you can't send out the full series.
- Eric
prev parent reply other threads:[~2020-01-07 3:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 2:33 [PATCH v2 0/3] Fscrypt support for casefolded encryption Daniel Rosenberg
2020-01-07 2:33 ` [PATCH v2 1/3] fscrypt: Add siphash and hash key for policy v2 Daniel Rosenberg
2020-01-07 4:02 ` Eric Biggers
2020-01-07 2:33 ` [PATCH v2 2/3] fscrypt: Don't allow v1 policies with casefolding Daniel Rosenberg
2020-01-07 3:35 ` Eric Biggers
2020-01-07 2:33 ` [PATCH v2 3/3] fscrypt: Change format of no-key token Daniel Rosenberg
2020-01-08 22:07 ` Eric Biggers
2020-01-07 3:26 ` Eric Biggers [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=20200107032659.GB705@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=drosen@google.com \
--cc=kernel-team@android.com \
--cc=krisman@collabora.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).