[CRYPTO] Allow AES C/ASM implementations to coexist
authorHerbert Xu <herbert@gondor.apana.org.au>
Sat, 5 Nov 2005 07:06:26 +0000 (18:06 +1100)
committerDavid S. Miller <davem@sunset.davemloft.net>
Mon, 9 Jan 2006 22:15:39 +0000 (14:15 -0800)
commitc8a19c91b5b488fed8cce04200a84c6a35c0bf0c
treee0296c60f7601c5a1d1cf5fa9afd0e38f92e6995
parent5cb1454b862ab3040b78364d58330262fea1ddba
[CRYPTO] Allow AES C/ASM implementations to coexist

As the Crypto API now allows multiple implementations to be registered
for the same algorithm, we no longer have to play tricks with Kconfig
to select the right AES implementation.

This patch sets the driver name and priority for all the AES
implementations and removes the Kconfig conditions on the C implementation
for AES.

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
arch/i386/crypto/aes.c
arch/x86_64/crypto/aes.c
crypto/Kconfig
crypto/aes.c
drivers/crypto/padlock-aes.c