From: James Bottomley <James.Bottomley@steeleye.com>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Summit support for pcibus <-> cpumask topology
Date: 14 Mar 2003 15:12:10 -0600 [thread overview]
Message-ID: <1047676332.5409.374.camel@mulgrave> (raw)
> This patch adds a new file, arch/i386/kernel/summit.c, for
> summit-specific code. Adds some structures to mach_mpparse.h. Also
> adds a hook in setup_arch() to dig out the PCI info, and stores it in
> the mp_bus_id_to_node[] array, where it can be read by the topology
> functions.
Wouldn't this file be better in arch/i386/mach-summit in keeping with
all the other subarch stuff?
While you're creating a separate file for summit, could you move the
summit specific variables (mpparse.c:x86_summit is the only one, I
think) into it so we can clean all the summit references out of the main
line?
Thanks,
James
next reply other threads:[~2003-03-14 21:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 21:12 James Bottomley [this message]
2003-03-15 1:41 ` [patch] Summit support for pcibus <-> cpumask topology [1/2] Matthew Dobson
2003-03-15 1:43 ` [patch] Summit support for pcibus <-> cpumask topology [2/2] Matthew Dobson
2003-03-15 1:46 ` [patch] NUMAQ subarchification Matthew Dobson
2003-03-15 2:05 ` Martin J. Bligh
2003-03-15 17:53 ` James Bottomley
2003-03-15 17:58 ` Martin J. Bligh
2003-03-16 2:53 ` Kai Germaschewski
2003-03-16 3:22 ` Martin J. Bligh
2003-03-16 5:05 ` James Bottomley
2003-03-16 5:55 ` Kai Germaschewski
2003-03-16 14:36 ` James Bottomley
2003-03-16 1:07 ` Alan Cox
2003-03-16 2:24 ` Martin J. Bligh
2003-03-16 4:31 ` James Bottomley
2003-03-18 1:58 ` Matthew Dobson
2003-03-18 16:16 ` James Bottomley
2003-03-18 16:30 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 20:30 [patch] Summit support for pcibus <-> cpumask topology Matthew Dobson
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=1047676332.5409.374.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.