From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
linux-next <linux-next@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Fix "attempt to move .org backwards" error
Date: Sat, 15 Feb 2014 10:02:31 -0800 [thread overview]
Message-ID: <52FFABB7.3090302@roeck-us.net> (raw)
In-Reply-To: <20140212162251.57472ed024ace170b49ec2fa@canb.auug.org.au>
On 02/11/2014 09:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 10 Dec 2013 10:26:10 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>>
>> On Tue, 2013-12-10 at 10:10 +1100, Stephen Rothwell wrote:
>>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>>> Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>
>>>
>>> Works for me. Thanks. I will add this to linux-next today if Ben
>>> doesn't add it to his tree.
>>
>> I will but probably not soon enough for your cut today
>
> As noted elsewhere, this did not completely fix the problem and I have
> been still getting this error from my allyesconfig builds for some time:
>
+allmodconfig in latest mainline.
> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> arch/powerpc/kernel/exceptions-64s.S:1312: Error: attempt to move .org backwards
>
> Could someone please fix this?
>
Guenter
next prev parent reply other threads:[~2014-02-15 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 19:10 [PATCH] powerpc: Fix "attempt to move .org backwards" error Mahesh J Salgaonkar
2013-12-09 23:10 ` Stephen Rothwell
2013-12-09 23:26 ` Benjamin Herrenschmidt
2014-02-12 5:22 ` Stephen Rothwell
2014-02-15 18:02 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-09 5:22 Guenter Roeck
2014-08-11 0:20 ` Stephen Rothwell
2014-08-11 16:25 ` Guenter Roeck
2013-04-26 3:51 Paul Mackerras
2013-04-26 4:13 ` Chen Gang
2013-04-27 9:34 ` Mike Qiu
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=52FFABB7.3090302@roeck-us.net \
--to=linux@roeck-us.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--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).