From: Simon Horman <horms@verge.net.au>
To: linux-kernel@vger.kernel.org,
Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [ARM] Fix hard_smp_processor_id compile error
Date: Tue, 15 May 2007 18:49:37 +0900 [thread overview]
Message-ID: <20070515094936.GC22359@verge.net.au> (raw)
In-Reply-To: <20070515090917.GA22359@verge.net.au>
On Tue, May 15, 2007 at 06:09:18PM +0900, Simon Horman wrote:
> On Tue, May 15, 2007 at 09:19:07AM +0100, Russell King wrote:
> > On Tue, May 15, 2007 at 11:18:50AM +0900, Simon Horman wrote:
> > > "Remove hardcoding of hard_smp_processor_id on UP systems",
> > > 2f4dfe206a2fc07099dfad77a8ea2f4b4ae2140f in Linus' tree, moved
> > > the definition of hard_smp_processor_id linux/smp.h to asm/smp.h
> > > for UP systems. This causes a regression on ARM as the definition
> > > was not added to asm-arm/smp.h.
> > >
> > > Cc: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
> > > Signed-off-by: Simon Horman <horms@verge.net.au>
> >
> > I took an alternative approach - since Integrator never had the complete
> > SMP support merged, I ripped it out of that platform. Whether realview
> > suffers from the same thing or not I'm not sure - uniprocessor realview
> > is not something covered by the ARM default configuration files, and
> > therefore kautobuild won't check that configuration.
>
> I can take a look into this. Is there a tree other than Linus'
> I should be working with?
Looking at Linus' it seems that for realview UP builds based on
realview_defconfig don't suffer hard_smp_processor_id breakage.
prev parent reply other threads:[~2007-05-15 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 2:18 [ARM] Fix hard_smp_processor_id compile error Simon Horman
2007-05-15 2:59 ` Fernando Luis Vázquez Cao
2007-05-15 4:48 ` Andrew Morton
2007-05-15 4:54 ` Simon Horman
2007-05-15 5:22 ` Andrew Morton
2007-05-15 5:28 ` Simon Horman
2007-05-15 8:19 ` Russell King
2007-05-15 9:09 ` Simon Horman
2007-05-15 9:49 ` Simon Horman [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=20070515094936.GC22359@verge.net.au \
--to=horms@verge.net.au \
--cc=akpm@linux-foundation.org \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-kernel@vger.kernel.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 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.