From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix generic build when CONFIG_SMP=n
Date: Tue, 24 Aug 2004 18:25:56 +0000 [thread overview]
Message-ID: <200408241125.56470.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200408131559.59229.jbarnes@engr.sgi.com>
On Friday, August 13, 2004 3:59 pm, Jesse Barnes wrote:
> This patch fixes the issues I saw with CONFIG_SMP=n when building a generic
> kernel with CONFIG_NUMA=y and CONFIG_DISCONTIGMEM=y. It's still pretty
> rough, but I'd appreciate comments and testing on other platforms. The
> per-cpu fixes are still pretty ugly--I'm sure I'm missing something that
> would make abstracting out per_cpu(cpu_info, cpu).node_data > mem_data[node].node_data much nicer looking.
>
> Fixing the build of generic kernels w/o CONFIG_NUMA or CONFIG_DISCONTIGMEM
> is left as an exercise for the reader. :)
No comments? Tony, do you think it's ready to apply?
Thanks,
Jesse
prev parent reply other threads:[~2004-08-24 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 22:59 [PATCH] fix generic build when CONFIG_SMP=n Jesse Barnes
2004-08-16 3:29 ` dann frazier
2004-08-16 22:23 ` Randy.Dunlap
2004-08-17 1:10 ` Jesse Barnes
2004-08-24 18:25 ` Jesse Barnes [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=200408241125.56470.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