[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWZ5=c6=+SneWnuC5Qz93ENxRD--DKz-m2VxudUFLyxGA@mail.gmail.com>
Date: Thu, 11 Apr 2013 19:23:09 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org
Subject: Re: linux-next: Tree for Apr 11 [ crypto: aesni-intel ]
On Thu, Apr 11, 2013 at 7:14 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Thu, Apr 11, 2013 at 10:30 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi all,
>>
>> Changes since 20130410:
>>
>> The tip tree gained conflicts against the net-next and pm trees.
>>
>> The driver-core tree gained a conflict against the tip tree.
>>
>> The arm-soc tree gained a conflict against the arm-current tree.
>>
>> The akpm tree lost a patch that turned up elsewhere.
>>
>> ----------------------------------------------------------------------------
>
> [ CC linux-crypto folks ]
>
> On Ubuntu/precise AMD64 I see:
>
> ERROR: "glue_xts_crypt_128bit_one" [arch/x86/crypto/aesni-intel.ko] undefined!
> ERROR: "glue_xts_crypt_128bit" [arch/x86/crypto/aesni-intel.ko] undefined!
> make[3]: *** [__modpost] Error 1
> make[2]: *** [modules] Error 2
>
> CONFIG_CRYPTO_AES=y
> CONFIG_CRYPTO_AES_X86_64=m
> CONFIG_CRYPTO_AES_NI_INTEL=m
>
> Full kernel-config attached.
>
>
> - Sedat -
Trying the fix "crypto: aesni_intel - fix Kconfig problem with
CRYPTO_GLUE_HELPER_X86" from [1].
- Sedat -
[1] http://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=110e7610190cc4693f26c05b43ea83468a0a925c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists