From: Simon Horman <horms@verge.net.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>,
linux-kernel@vger.kernel.org,
"Russell King" <rmk@arm.linux.org.uk>
Subject: Re: [ARM] Fix hard_smp_processor_id compile error
Date: Tue, 15 May 2007 13:54:23 +0900 [thread overview]
Message-ID: <20070515045422.GD13708@verge.net.au> (raw)
In-Reply-To: <20070514214818.16b36610.akpm@linux-foundation.org>
On Mon, May 14, 2007 at 09:48:18PM -0700, Andrew Morton wrote:
> On Tue, 15 May 2007 11:59:41 +0900 Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> wrote:
>
> > On Tue, 2007-05-15 at 11:18 +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.
> > Hi Simon!
> >
> > Thank you for catching and fixing these compile errors. I should install
> > a cross-compiler ASAP.
>
> Mine are at http://userweb.kernel.org/~akpm/cross-compilers/
Do you have / know of tools to create a set of configs for testing?
What I am thinking of is something that takes the default configs,
then toggles SMP, PREEMT and stuff like that, testing all the
permutations.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next prev parent reply other threads:[~2007-05-15 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 2:18 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 [this message]
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
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=20070515045422.GD13708@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 \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®