From: Danny Tsen <dtsen@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dtsen@us.ibm.com, nayna@linux.ibm.com,
linux-kernel@vger.kernel.org, appro@cryptogams.org,
linux-crypto@vger.kernel.org, ltcgcw@linux.vnet.ibm.com,
leitao@debian.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 5/5] Update Kconfig and Makefile.
Date: Tue, 25 Apr 2023 07:04:09 -0500 [thread overview]
Message-ID: <1202328d-de94-7e9d-c0e8-bb1bd3e9a988@linux.ibm.com> (raw)
In-Reply-To: <ZEdpHDpm19XwN3dG@gondor.apana.org.au>
I was not sure at the time when I use IS_REACHABLE. Will fix it in init
code.
Thanks.
-Danny
On 4/25/23 12:46 AM, Herbert Xu wrote:
> On Mon, Apr 24, 2023 at 02:47:26PM -0400, Danny Tsen wrote:
>> +config CRYPTO_CHACHA20_P10
>> + tristate "Ciphers: ChaCha20, XChacha20, XChacha12 (P10 or later)"
>> + depends on PPC64 && CPU_LITTLE_ENDIAN
>> + select CRYPTO_SKCIPHER
> I thought your IS_REACHABLE test was so that you could build this
> without the Crypto API? Colour me confused.
>
> Cheers,
prev parent reply other threads:[~2023-04-25 12:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 18:47 [PATCH 0/5] crypto: Accelerated Chacha20/Poly1305 implementation Danny Tsen
2023-04-24 18:47 ` [PATCH 1/5] An optimized Chacha20 implementation with 8-way unrolling for ppc64le Danny Tsen
2023-04-24 20:40 ` Elliott, Robert (Servers)
2023-04-24 23:07 ` Danny Tsen
2023-04-25 12:02 ` Michael Ellerman
2023-04-25 12:08 ` Danny Tsen
2023-04-26 8:19 ` David Laight
2023-04-24 18:47 ` [PATCH 2/5] Glue code for optmized Chacha20 implementation " Danny Tsen
2023-04-25 5:37 ` Herbert Xu
2023-04-25 5:40 ` Herbert Xu
2023-04-25 5:41 ` Herbert Xu
2023-04-25 11:53 ` Danny Tsen
2023-04-24 18:47 ` [PATCH 3/5] An optimized Poly1305 implementation with 4-way unrolling " Danny Tsen
2023-04-24 18:47 ` [PATCH 4/5] Glue code for optmized Poly1305 implementation " Danny Tsen
2023-04-25 5:44 ` Herbert Xu
2023-04-25 11:58 ` Danny Tsen
2023-04-24 18:47 ` [PATCH 5/5] Update Kconfig and Makefile Danny Tsen
2023-04-25 5:46 ` Herbert Xu
2023-04-25 12:04 ` Danny Tsen [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=1202328d-de94-7e9d-c0e8-bb1bd3e9a988@linux.ibm.com \
--to=dtsen@linux.ibm.com \
--cc=appro@cryptogams.org \
--cc=dtsen@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ltcgcw@linux.vnet.ibm.com \
--cc=nayna@linux.ibm.com \
/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).