From: Herbert Xu <herbert@gondor•apana.org.au>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: 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 11:46:46 +1100 [thread overview]
Message-ID: <20120322004646.GA8489@gondor.apana.org.au> (raw)
In-Reply-To: <4F6A74E3.7080901@xenotime.net>
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.
--
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:[~2012-03-22 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 7:59 linux-next: Tree for Mar 15 Stephen Rothwell
2012-03-15 8:02 ` Geert Uytterhoeven
2012-03-15 8:17 ` Stephen Rothwell
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 [this message]
2012-03-22 21:18 ` H. Peter Anvin
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
2012-03-15 15:58 ` linux-next: Tree for Mar 15 (staging/android/ram_console.c) Randy Dunlap
2012-03-15 21:03 ` Greg Kroah-Hartman
2012-03-15 21:39 ` 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=20120322004646.GA8489@gondor.apana.org.au \
--to=herbert@gondor$(echo .)apana.org.au \
--cc=jussi.kivilinna@mbnet$(echo .)fi \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@xenotime$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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