From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Fix IA64 build with separate source and build trees.
Date: Thu, 09 Oct 2003 01:53:46 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106566459714625@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106565735409518@msgid-missing>
>>>>> On Thu, 9 Oct 2003 11:24:47 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Main advantage is it makes this bit of code almost identical
Peter> between architectures, so that when someone updates it a
Peter> simple grep will find it everywhere. And yes, it should be
Peter> ${ARCH} everywhere htat there's identical code between
Peter> architectures (which means everywhere, for simplicity as to
Peter> know when to use what)
I think we're going in circles. Originally, I had $(ARCH) for similar
reasons as you state and then they got replaced by ia64 in the big
Makefile rewrite. I don't really care much one way or the other, but
let's be consistent. AFAIK, currently everybody is using the
architecture name, so we probably should stick to that.
--david
prev parent reply other threads:[~2003-10-09 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 23:52 [PATCH] Fix IA64 build with separate source and build trees Peter Chubb
2003-10-09 0:21 ` Matthew Wilcox
2003-10-09 1:24 ` Peter Chubb
2003-10-09 1:53 ` David Mosberger [this message]
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=marc-linux-ia64-106566459714625@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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