From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: omap2plus_defconfig not building
Date: Thu, 23 Dec 2010 20:30:46 +0000 [thread overview]
Message-ID: <20101223203046.GR3636@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101223195503.GN7771@atomide.com>
On Thu, Dec 23, 2010 at 11:55:03AM -0800, Tony Lindgren wrote:
> * Catalin Marinas <catalin.marinas@arm.com> [101108 01:38]:
> > On Mon, 2010-11-08 at 06:05 +0000, Anand Gadiyar wrote:
> > > I can't find this patch in linux-next. Hope we haven't missed it.
> > > Tony acked this btw.
> > >
> > > Strangely, the omap2plus_defconfig in v2.6.37-rc1 no longer gets
> > > CONFIG_SWP_EMULATE enabled even without this patch - I can't figure
> > > out why.
That'll be because swap emulation isn't in v2.6.37-rc1. It's queued
for 2.6.38's merge window.
> > Russell had a better idea for handling this, not sure whether it went
> > into -next. It was basically adding -march=armv7-a to
> > CFLAGS_swp_emulate.o in arch/arm/kernel/Makefile since we can't trigger
> > an undef fault for SWP on ARMv6 anyway.
> >
> > If it's not in yet, I can submit a patch.
It's also queued for 2.6.38, but there is an issue with the latest gcc
stuffing a .armv7 directive (or whatever) at the beginning of its
output, thereby overriding the -Wa,-march=armv7-a on the command line.
I think someone's looking at fixing GCC.
This stuff _is_ in linux-next, and has been in linux-next for ages.
next prev parent reply other threads:[~2010-12-23 20:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 10:18 linux-next: omap2plus_defconfig not building Anand Gadiyar
2010-10-19 11:37 ` Catalin Marinas
2010-10-19 12:14 ` Anand Gadiyar
2010-10-19 22:49 ` Tony Lindgren
2010-11-08 6:05 ` Anand Gadiyar
2010-11-08 9:38 ` Uwe Kleine-König
2010-11-08 9:48 ` Catalin Marinas
2010-11-08 10:14 ` Russell King - ARM Linux
2010-11-08 10:20 ` Catalin Marinas
2010-11-08 10:25 ` Russell King - ARM Linux
2010-11-08 10:31 ` Catalin Marinas
2010-11-25 13:54 ` Anand Gadiyar
2010-11-25 16:50 ` Russell King - ARM Linux
2010-11-26 11:35 ` Anand Gadiyar
2010-11-26 11:45 ` Russell King - ARM Linux
2010-11-26 12:22 ` Will Deacon
2010-11-26 12:28 ` Russell King - ARM Linux
2010-11-26 12:38 ` Catalin Marinas
2010-11-26 12:55 ` Dave Martin
2010-11-26 13:00 ` Russell King - ARM Linux
2010-11-26 13:31 ` Dave Martin
2010-11-26 13:53 ` Russell King - ARM Linux
2010-11-26 12:33 ` Russell King - ARM Linux
2010-12-23 19:55 ` Tony Lindgren
2010-12-23 20:15 ` Tony Lindgren
2010-12-23 20:30 ` Russell King - ARM Linux [this message]
2010-12-23 21:06 ` Tony Lindgren
2011-01-07 3:59 ` Tony Lindgren
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=20101223203046.GR3636@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).