From: Dongsoo Lee <letrhee@nsr.re.kr>
To: 'Herbert Xu' <herbert@gondor.apana.org.au>,
"'David S. Miller'" <davem@davemloft.net>,
'Jens Axboe' <axboe@kernel.dk>,
'Eric Biggers' <ebiggers@kernel.org>,
"'Theodore Y. Ts'o'" <tytso@mit.edu>,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
'Thomas Gleixner' <tglx@linutronix.de>,
'Ingo Molnar' <mingo@redhat.com>,
'Borislav Petkov' <bp@alien8.de>,
'Dave Hansen' <dave.hansen@linux.intel.com>,
x86@kernel.org, "'H. Peter Anvin'" <hpa@zytor.com>,
'Dongsoo Lee' <letrhee@nsr.re.kr>
Cc: linux-crypto@vger.kernel.org, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH v6 0/5] crypto: LEA block cipher implementation
Date: Mon, 18 Dec 2023 16:33:01 +0900 [thread overview]
Message-ID: <004701da3184$6e090560$4a1b1020$@nsr.re.kr> (raw)
In-Reply-To: <20231205010329.21996-1-letrehee@nsr.re.kr>
(Resend mail because of an error)
Hello,
I'm checking in on the status of the patch submitted to the Linux kernel group. I understand the review process takes time, and we appreciate your team's efforts.
While awaiting review, is there anything specific we can do to enhance the patch's acceptance chances? Your guidance would be greatly appreciated.
Thank you,
Dongsoo Lee
prev parent reply other threads:[~2023-12-18 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 1:03 [PATCH v6 0/5] crypto: LEA block cipher implementation Dongsoo Lee
2023-12-05 1:03 ` [PATCH v6 1/5] " Dongsoo Lee
2023-12-05 1:03 ` [PATCH v6 2/5] crypto: add LEA testmgr tests Dongsoo Lee
2023-12-05 1:03 ` [PATCH v6 3/5] blk-crypto: Add LEA-256-XTS blk-crypto support Dongsoo Lee
2023-12-05 1:03 ` [PATCH v6 4/5] fscrypt: Add LEA-256-XTS, LEA-256-CTS support Dongsoo Lee
2023-12-05 1:03 ` [PATCH v6 5/5] crypto: LEA block cipher x86_64 optimization Dongsoo Lee
2023-12-18 7:33 ` Dongsoo Lee [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='004701da3184$6e090560$4a1b1020$@nsr.re.kr' \
--to=letrhee@nsr.re.kr \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jaegeuk@kernel.org \
--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=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=x86@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 read-only IMAP folder(s) and NNTP newsgroup(s).