linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	colpatch@us.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] NUMAQ subarchification
Date: 15 Mar 2003 22:31:43 -0600	[thread overview]
Message-ID: <1047789106.1964.189.camel@mulgrave> (raw)
In-Reply-To: <1047776836.1327.11.camel@irongate.swansea.linux.org.uk>

On Sat, 2003-03-15 at 19:07, Alan Cox wrote:
> It was fixed in about 2.5.50-ac. I thought Linus had picked up the 
> improved version of mach-default* too. Its used extensively for stuff
> like PC9800 which is deeply un-PC

Actually, we have all that in the mainline.  It was the .h fallback to
mach-defaults.

The issue here is that mach-numaq and mach-summit are very PC like and
so don't need any of the hooks that are in setup.c, thus they'd like to
share setup.c from mach-default.  Likewise, they have the same topology
file, I think (although this time it would be different from
mach-default since we can pull the numa pieces out).  Prior to the build
changes, VPATH would solve this problem (I used to use it to get
trampoline.o for voyager).  However, now, the best I think we can do is
to cat the file across.

James



  parent reply	other threads:[~2003-03-16  4:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 21:12 [patch] Summit support for pcibus <-> cpumask topology James Bottomley
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 [this message]
2003-03-18  1:58       ` Matthew Dobson
2003-03-18 16:16         ` James Bottomley
2003-03-18 16:30           ` 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=1047789106.1964.189.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=colpatch@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).