From: tony@bakeyournoodle•com (Tony Breeds)
To: Michael Ellerman <michael@ellerman•id.au>
Cc: LinuxPPC-dev <linuxppc-dev@ozlabs•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH 2.6.26?] Raise the upper limit of NR_CPUS.
Date: Mon, 21 Apr 2008 11:41:34 +1000 [thread overview]
Message-ID: <20080421014134.GF20457@bakeyournoodle.com> (raw)
In-Reply-To: <1208514829.8424.0.camel@concordia>
On Fri, Apr 18, 2008 at 08:33:44PM +1000, Michael Ellerman wrote:
> What happens on non prom-init platforms?
.... Um yeah they wont work.
I'll try a slightly different approach.
Yours Tony
linux.conf.au http://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2008-04-21 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 5:33 [PATCH 2.6.26?] Raise the upper limit of NR_CPUS Tony Breeds
2008-04-18 10:33 ` Michael Ellerman
2008-04-21 1:41 ` Tony Breeds [this message]
2008-04-21 2:03 ` Benjamin Herrenschmidt
2008-04-21 9:05 ` Michael Ellerman
2008-04-21 9:24 ` Benjamin Herrenschmidt
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=20080421014134.GF20457@bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=michael@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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