From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: cpu_to_node_map on UP systems
Date: Wed, 09 Mar 2005 22:51:18 +0000 [thread overview]
Message-ID: <200503091451.18448.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1110350919.9439.16.camel@localhost>
On Wednesday, March 9, 2005 11:31 am, Luck, Tony wrote:
> Yes, tiger builds ok with SMP=n (if you pull from the
> linux-ia64-test-2.6.12 you'll also gets Bjorn's fix to iosapic so the the
> resulting kernel will boot, rather than hang).
>
> There are still problems with building the generic kernel with SMP=n
I thought we had worked all these out awhile ago? I assume you're merging all
this stuff as fast as you can now that 2.6.12 is open? Or do you need me to
resend? If so, let me know when you've got the bulk of your queue merged and
I can fix things up, rediff and resend.
Thanks,
Jesse
next prev parent reply other threads:[~2005-03-09 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 6:48 cpu_to_node_map on UP systems dann frazier
2005-03-09 10:37 ` Darren Williams
2005-03-09 19:31 ` Luck, Tony
2005-03-09 22:21 ` Christoph Hellwig
2005-03-09 22:51 ` Jesse Barnes [this message]
2005-03-10 0:13 ` Luck, Tony
2005-03-10 1:28 ` Darren Williams
2005-03-10 17:19 ` dann frazier
2005-03-10 21:09 ` Luck, Tony
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=200503091451.18448.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox