From: "Martin J. Bligh" <mbligh@aracnet.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [patch] NUMAQ subarchification
Date: Sat, 15 Mar 2003 09:58:02 -0800 [thread overview]
Message-ID: <16190000.1047751081@[10.10.2.4]> (raw)
In-Reply-To: <1047750799.1964.72.camel@mulgrave>
>> No, *please* don't do this. Subarch for .c files is *broken*.
>
> It is the place designed for code belonging only to one subarch.
That doesn't mean it's not broken.
>> Let's just stick with your original patch - it's fine.
>
> No, it's not. The object of the subarch is to remove all subarch
> specific files from the main i386/kernel directory.
It needs fixing to avoid the duplication first ... after that it'll
be a fine idea. Until that, I'm not moving any code under there.
M.
next prev parent reply other threads:[~2003-03-15 17:47 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 [this message]
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
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='16190000.1047751081@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=James.Bottomley@SteelEye.com \
--cc=colpatch@us.ibm.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®