From: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org,
Herbert Xu <herbert@gondor.hengli.com.au>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] crypto: serpent-sse2 - should select CRYPTO_CRYPTD
Date: Thu, 24 Nov 2011 08:37:41 +0200 [thread overview]
Message-ID: <20111124063741.17986.23462.stgit@localhost6.localdomain6> (raw)
In-Reply-To: <4ECD527E.8000506@xenotime.net>
Since serpent_sse2_glue.c uses cryptd, CRYPTO_SERPENT_SSE2_X86_64 and
CRYPTO_SERPENT_SSE2_586 should be selecting CRYPTO_CRYPTD.
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
---
crypto/Kconfig | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 16e0c13..b8d1b10 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -770,6 +770,7 @@ config CRYPTO_SERPENT_SSE2_X86_64
tristate "Serpent cipher algorithm (x86_64/SSE2)"
depends on X86 && 64BIT
select CRYPTO_ALGAPI
+ select CRYPTO_CRYPTD
select CRYPTO_SERPENT
help
Serpent cipher algorithm, by Anderson, Biham & Knudsen.
@@ -787,6 +788,7 @@ config CRYPTO_SERPENT_SSE2_586
tristate "Serpent cipher algorithm (i586/SSE2)"
depends on X86 && !64BIT
select CRYPTO_ALGAPI
+ select CRYPTO_CRYPTD
select CRYPTO_SERPENT
help
Serpent cipher algorithm, by Anderson, Biham & Knudsen.
next prev parent reply other threads:[~2011-11-24 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 4:44 linux-next: Tree for Nov 23 Stephen Rothwell
2011-11-23 20:07 ` linux-next: Tree for Nov 23 (crypto) Randy Dunlap
2011-11-24 6:37 ` Jussi Kivilinna [this message]
2011-11-24 18:35 ` [PATCH] crypto: serpent-sse2 - should select CRYPTO_CRYPTD Randy Dunlap
2011-11-30 8:18 ` Herbert Xu
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=20111124063741.17986.23462.stgit@localhost6.localdomain6 \
--to=jussi.kivilinna@mbnet.fi \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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