[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUXR-dYRWkkz=V8=zn7cO=G1Ksa0bNweGn6kbYpjPn4mTg@mail.gmail.com>
Date: Thu, 11 Apr 2013 19:14:31 +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 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 -
View attachment "config.txt" of type "text/plain" (112227 bytes)
Powered by blists - more mailing lists