Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 6 Jan 2020 19:26:59 -0800
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
Message-ID: <20200107032659.GB705@sol.localdomain>
References: <20200107023323.38394-1-drosen@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200107023323.38394-1-drosen@google.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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