From: "H. Peter Anvin" <hpa@zytor.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Jussi Kivilinna <jussi.kivilinna@mbnet.fi>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] crypto: camellia-x86_64 - module init/exit functions should be static
Date: Thu, 22 Mar 2012 14:18:01 -0700 [thread overview]
Message-ID: <4F6B9709.1040701@zytor.com> (raw)
In-Reply-To: <20120322004646.GA8489@gondor.apana.org.au>
On 03/21/2012 05:46 PM, Herbert Xu wrote:
> On Wed, Mar 21, 2012 at 05:40:03PM -0700, Randy Dunlap wrote:
>> On 03/15/2012 01:11 PM, Jussi Kivilinna wrote:
>>
>>> This caused conflict with twofish-x86_64-3way when compiled into kernel,
>>> same function names and not static.
>>
>> Have these patches been merged anywhere?
>> I'm still seeing build problems in linux-next 20120321.
>
> Thanks for the reminder, I'll push these through today.
Please push these to Linus ASAP, it is breaking the x86-64 allyesconfig
build upstream right now.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-03-22 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120315185935.a0c475a30b2836765273a1e5@canb.auug.org.au>
2012-03-15 15:48 ` linux-next: Tree for Mar 15 (crypto) Randy Dunlap
2012-03-15 20:05 ` Jussi Kivilinna
2012-03-15 20:11 ` [PATCH 1/2] crypto: camellia-x86_64 - module init/exit functions should be static Jussi Kivilinna
2012-03-15 22:49 ` Randy Dunlap
2012-03-22 0:40 ` Randy Dunlap
2012-03-22 0:46 ` Herbert Xu
2012-03-22 21:18 ` H. Peter Anvin [this message]
2012-03-23 0:42 ` Herbert Xu
2012-03-15 20:11 ` [PATCH 2/2] crypto: twofish-x86_64-3way " Jussi Kivilinna
2012-03-15 22:49 ` Randy Dunlap
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=4F6B9709.1040701@zytor.com \
--to=hpa@zytor.com \
--cc=herbert@gondor.hengli.com.au \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).