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
Date: Mon, 21 Aug 2023 21:53:52 -0700 [thread overview]
Message-ID: <20230822045352.GB1661@sol.localdomain> (raw)
In-Reply-To: <000001d9d3b8$bca8e9d0$35fabd70$@nsr.re.kr>
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
prev parent reply other threads:[~2023-08-22 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 5:03 [PATCH v4 0/4] crypto: LEA block cipher implementation Dongsoo Lee
2023-06-30 5:03 ` [PATCH v4 1/4] " Dongsoo Lee
2023-06-30 5:03 ` [PATCH v4 2/4] crypto: add LEA testmgr tests Dongsoo Lee
2023-06-30 5:03 ` [PATCH v4 3/4] blk-crypto: Add LEA-256-XTS blk-crypto support Dongsoo Lee
2023-06-30 5:03 ` [PATCH v4 4/4] fscrypt: Add LEA-256-XTS, LEA-256-CTS support Dongsoo Lee
2023-08-20 22:50 ` [PATCH v4 0/4] crypto: LEA block cipher implementation Dongsoo Lee
2023-08-22 4:53 ` 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=20230822045352.GB1661@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jaegeuk@kernel.org \
--cc=letrhee@nsr.re.kr \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox