Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 21 Aug 2023 21:53:52 -0700
From:   Eric Biggers <ebiggers@kernel.org>
To:     Dongsoo Lee <letrhee@nsr.re.kr>
Cc:     'Herbert Xu' <herbert@gondor.apana.org.au>,
        "'David S. Miller'" <davem@davemloft.net>,
        'Jens Axboe' <axboe@kernel.dk>,
        "'Theodore Y. Ts'o'" <tytso@mit.edu>,
        'Jaegeuk Kim' <jaegeuk@kernel.org>,
        linux-crypto@vger.kernel.org, linux-block@vger.kernel.org,
        linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] crypto: LEA block cipher implementation
Message-ID: <20230822045352.GB1661@sol.localdomain>
References: <20230630050323.984216-1-letrhee@nsr.re.kr>
 <000001d9d3b8$bca8e9d0$35fabd70$@nsr.re.kr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000001d9d3b8$bca8e9d0$35fabd70$@nsr.re.kr>
Precedence: bulk

On Mon, Aug 21, 2023 at 07:50:37AM +0900, Dongsoo Lee wrote:
> Hello.
> 
> Is there any further progress on the patch we submitted and the additional fscrypt documentation? 
> 
> https://lore.kernel.org/linux-fscrypt/20230630064811.22569-1-ebiggers@kernel.org/T/#u.
> 
> If the LEA cipher is accepted, we would like to add a SIMD implementation for it.

I already applied 'fscrypt: improve the "Encryption modes and usage" section'
(https://lore.kernel.org/r/20230630064811.22569-2-ebiggers@kernel.org) for 6.6.

I don't object to the fscrypt support for LEA, but I'm not going to apply it
until the crypto API support is accepted.

- Eric