From: john stultz <johnstul@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
lkml <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [RFC] [PATCH] subarch cleanup
Date: 21 Nov 2002 10:55:54 -0800 [thread overview]
Message-ID: <1037904954.7576.62.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <20021121183304.GA1144@mars.ravnborg.org>
On Thu, 2002-11-21 at 10:33, Sam Ravnborg wrote:
> > ifdef CONFIG_VISWS
> > -MACHINE := mach-visws
> > +MACHINE_C := mach-visws
> > +MACHINE_H := mach-visws
> > else
> > -MACHINE := mach-generic
> > +MACHINE_C := mach-generic
> > +MACHINE_H := mach-generic
>
> No reason to have two different variables assigned the same value.
Actually, in some cases, such as summit, we only have one header file
that is different from generic. We don't want to replicate all the
generic .c files, So in that case MACHINE_C := mach-generic and
MACHINE_H := mach-summit.
There very well could be a better way to do this, but splitting up the
.h files which fall back to generic nicely, and the .c files which don't
seemed to make the most sense.
> If you are modifying this anyway consider something like:
> machine-y := mach-generic
> machine-$(CONFIG_VISWS) := mach-visws
>
> And then replace $(MACHINE) with $(machine-y).
> This makes it much cleaner to add summit for example.
I agree, it could be cleaned up. I'll see if I can't clean it up
further.
thanks for the feedback
-john
next prev parent reply other threads:[~2002-11-21 18:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 0:00 john stultz
2002-11-21 18:33 ` Sam Ravnborg
2002-11-21 18:35 ` Martin J. Bligh
2002-11-21 19:34 ` Russell King
2002-11-21 21:47 ` Martin J. Bligh
2002-11-22 15:00 ` J.E.J. Bottomley
2002-11-22 15:42 ` Martin J. Bligh
2002-11-22 16:40 ` J.E.J. Bottomley
2002-11-22 16:57 ` Christoph Hellwig
2002-11-22 17:20 ` Martin J. Bligh
2002-11-22 17:55 ` J.E.J. Bottomley
2002-11-21 18:55 ` john stultz [this message]
2002-11-21 19:15 ` Sam Ravnborg
2002-11-21 20:27 ` Alan Cox
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=1037904954.7576.62.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=sam@ravnborg.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®