From: Herbert Xu <herbert@gondor.apana.org.au>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 11 [ crypto: aesni-intel ]
Date: Fri, 12 Apr 2013 10:13:36 +0800 [thread overview]
Message-ID: <20130412021336.GA14735@gondor.apana.org.au> (raw)
In-Reply-To: <CA+icZUXR-dYRWkkz=V8=zn7cO=G1Ksa0bNweGn6kbYpjPn4mTg@mail.gmail.com>
On Thu, Apr 11, 2013 at 07:14:31PM +0200, Sedat Dilek wrote:
> On Thu, Apr 11, 2013 at 10:30 AM, Stephen Rothwell <sfr@canb.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
Should be fixed by:
commit 110e7610190cc4693f26c05b43ea83468a0a925c
Author: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Date: Wed Apr 10 18:39:20 2013 +0300
crypto: aesni_intel - fix Kconfig problem with CRYPTO_GLUE_HELPER_X86
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2013-04-12 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 17:14 linux-next: Tree for Apr 11 [ crypto: aesni-intel ] Sedat Dilek
2013-04-11 17:23 ` Sedat Dilek
2013-04-12 2:13 ` Herbert Xu [this message]
2013-04-12 14:46 ` Sedat Dilek
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=20130412021336.GA14735@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).