From: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code)
Date: Thu, 12 Mar 2015 12:27:32 -0300 [thread overview]
Message-ID: <20150312152732.GA8966@bluepex.com> (raw)
In-Reply-To: <20150312035327.GA14659@gondor.apana.org.au>
A little bit later, but thank you guys for fix it.
The issue seems happens just in BE machines, and using _GLOBAL instead
.globl seems fix it so build the correct vmx-crypto.ko. On LE it does
not happens.
On Thu, Mar 12, 2015 at 02:53:27PM +1100, Herbert Xu wrote:
> On Wed, Mar 11, 2015 at 08:51:32PM -0700, Guenter Roeck wrote:
> >
> > Yes, this helps.
> >
> > Feel free to add
> >
> > Tested-by: Guenter Roeck <linux@roeck-us.net>
>
> Thanks for testing and the quick feedback.
> --
> 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:[~2015-03-12 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 5:35 linux-next: Tree for Mar 11 Stephen Rothwell
2015-03-11 15:47 ` linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code) Guenter Roeck
2015-03-12 1:23 ` Herbert Xu
2015-03-12 2:43 ` Guenter Roeck
2015-03-12 3:28 ` Herbert Xu
2015-03-12 3:51 ` Guenter Roeck
2015-03-12 3:53 ` Herbert Xu
2015-03-12 15:27 ` Leonidas S. Barbosa [this message]
2015-03-11 15:51 ` linux-next: Tree for Mar 11 (arm build failure, ASoC) Guenter Roeck
2015-03-12 6:53 ` Peter Ujfalusi
2015-03-11 15:55 ` linux-next: Tree for Mar 11 (arm:multi_v5_defconfig build failure) Guenter Roeck
2015-03-11 16:21 ` Simon Guinot
2015-03-11 16:26 ` Gregory CLEMENT
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=20150312152732.GA8966@bluepex.com \
--to=leosilva@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.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).