From: James Bottomley <James.Bottomley@steeleye.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
colpatch@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] NUMAQ subarchification
Date: 15 Mar 2003 23:05:55 -0600 [thread overview]
Message-ID: <1047791157.1963.212.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44.0303152036250.27065-100000@chaos.physics.uiowa.edu>
On Sat, 2003-03-15 at 20:53, Kai Germaschewski wrote:
> I think VPATH has never been meant to be used for anything like this, it
> could be make to work, though it would interfere with the separate src/obj
> thing. But I don't think it's a good idea, we'll have object files
> magically appear without any visible source file, that's just too obscure.
Well...There is a slightly different solution.
What if the summit/numaq setup.c simply contained
#include "../mach-default/setup.c"
?
Not that I like doing this, but it solves the "magic" appearace of the
object file and it's perfectly clear to anyone editing the file where it
really comes from.
James
next prev parent reply other threads:[~2003-03-16 4:58 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 [this message]
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=1047791157.1963.212.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=colpatch@us.ibm.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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