From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: MAX_IO_APICS #ifdef'd wrongly
Date: Fri, 17 Jan 2003 15:14:17 -0800 [thread overview]
Message-ID: <20030117231417.GT919@holomorphy.com> (raw)
In-Reply-To: <224570000.1042818820@titus>
On Fri, Jan 17, 2003 at 07:53:41AM -0800, Martin J. Bligh wrote:
> Summit needs this too, so it should really be CONFIG_NUMA at least.
> Ideally this would go into subarch if we can move it cleanly (hint, hint ;-))
> But other than that, yes ... I'll merge it.
> Thanks,
I shot for the one liner that fixed the case I could test. Shoving it
into subarch is cleaner, but needs more code movement and changes the
prior semantics. The prior semantics were broken for larger Summit
configurations, hmm. Maybe _all_ the array sizes should go into some
kind of subarch analogue of param.h, e.g. mach_param.h
The only one I can think of that doesn't fly is NR_IRQS; once there
are more interrupt sources than FIRST_SYSTEM_VECTOR - FIRST_DEVICE_VECTOR
the whole of arch/i386/ appears to explode.
Someone somewhere should probably take notice of that.
Bill
next prev parent reply other threads:[~2003-01-17 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 9:00 MAX_IO_APICS #ifdef'd wrongly William Lee Irwin III
2003-01-17 15:53 ` Martin J. Bligh
2003-01-17 23:14 ` William Lee Irwin III [this message]
2003-01-18 0:52 ` Martin J. Bligh
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=20030117231417.GT919@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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