From: Max Filippov <jcmvbkbc@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Lad@roeck-us.net, Prabhakar <prabhakar.csengg@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Mack <daniel@zonque.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits)
Date: Wed, 1 Apr 2015 06:16:46 +0300 [thread overview]
Message-ID: <CAMo8Bf+D0wrvVt5H2XTqpHOo=6x2jZdwbOg7pW=zXhv2ZCBM2g@mail.gmail.com> (raw)
In-Reply-To: <20150331161640.GA16540@roeck-us.net>
On Tue, Mar 31, 2015 at 7:16 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> xtensa
>
> Lots of 'dangerous relocation: l32r: literal placed after use' all over the
> place, causing all xtensa builds to fail.
>
> Introduced by commit 779c88c94c34 ("ARM: 8321/1: asm-generic: introduce
> .text.fixup input section").
I'm looking at it.
--
Thanks.
-- Max
prev parent reply other threads:[~2015-04-01 3:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:02 linux-next: Tree for Mar 31 Stephen Rothwell
2015-03-31 16:16 ` linux-next: Tree for Mar 31 (build failures and culprits) Guenter Roeck
2015-03-31 23:07 ` Greg Kroah-Hartman
2015-03-31 23:24 ` Michael Ellerman
2015-04-01 2:18 ` Guenter Roeck
2015-04-01 3:01 ` Michael Ellerman
2015-04-01 3:13 ` Guenter Roeck
2015-03-31 23:42 ` Stephen Rothwell
2015-04-01 2:24 ` Guenter Roeck
2015-04-01 2:45 ` Guenter Roeck
2015-04-01 6:13 ` Daniel Mack
2015-04-01 2:17 ` Guenter Roeck
2015-04-01 8:08 ` Russell King - ARM Linux
2015-04-01 12:23 ` Guenter Roeck
2015-04-01 3:16 ` Max Filippov [this message]
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='CAMo8Bf+D0wrvVt5H2XTqpHOo=6x2jZdwbOg7pW=zXhv2ZCBM2g@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=Lad@roeck-us.net \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=daniel@zonque.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mperttunen@nvidia.com \
--cc=prabhakar.csengg@gmail.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=treding@nvidia.com \
/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).