From: Sedat Dilek Subject: Re: linux-next: Tree for Apr 11 [ crypto: aesni-intel ] Date: Thu, 11 Apr 2013 19:23:09 +0200 Message-ID: References: Reply-To: sedat.dilek@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Herbert Xu , "David S. Miller" , linux-crypto@vger.kernel.org To: Stephen Rothwell Return-path: Received: from mail-we0-f178.google.com ([74.125.82.178]:33027 "EHLO mail-we0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754138Ab3DKRXL (ORCPT ); Thu, 11 Apr 2013 13:23:11 -0400 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: On Thu, Apr 11, 2013 at 7:14 PM, Sedat Dilek wrote: > On Thu, Apr 11, 2013 at 10:30 AM, Stephen Rothwell 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