From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Lindgren <tony@atomide.com>
Subject: Re: linux-next: build failure after merge of the arm-current tree
Date: Fri, 10 Apr 2015 08:28:31 +0100 [thread overview]
Message-ID: <20150410072830.GA12732@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150410102933.0a79020d@canb.auug.org.au>
On Fri, Apr 10, 2015 at 10:29:33AM +1000, Stephen Rothwell wrote:
> Hi Russell,
>
> After merging the arm-current tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/mm/proc-v7.S: Assembler messages:
> arch/arm/mm/proc-v7.S:535: Error: invalid operands (*ABS* and .text sections) for `|'
> arch/arm/mm/proc-v7.S:535: Error: invalid operands (*ABS* and .text sections) for `|'
>
> Caused by commit f2fd12256533 ("ARM: proc-v7: avoid errata 430973
> workaround for non-Cortex A8 CPUs").
>
> I have reverted that commit for today.
The ARM autobuilders built the tree I pushed out with no problems. The
commit itself isn't quite correct, but the merge head of the for-next
branch /is/ correct. I've now fixed that, but I don't see why you would
have hit this.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-04-10 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 0:29 linux-next: build failure after merge of the arm-current tree Stephen Rothwell
2015-04-10 7:28 ` Russell King - ARM Linux [this message]
2015-04-10 8:08 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2018-04-18 3:31 Stephen Rothwell
2018-04-18 17:54 ` Russell King
2018-04-18 18:17 ` Russell King
2018-04-18 23:51 ` Stephen Rothwell
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=20150410072830.GA12732@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.