From: ebiederm@xmission.com (Eric W. Biederman)
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Greg KH <greg@kroah.com>, "Martin J. Bligh" <mbligh@aracnet.com>,
Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@codemonkey.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Summit support for 2.5 [0/4]
Date: 13 Oct 2002 23:46:24 -0600 [thread overview]
Message-ID: <m1adlhlgi7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210132145210.4554-100000@chaos.physics.uiowa.edu>
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> writes:
> On Sun, 13 Oct 2002, Greg KH wrote:
>
> > +ifeq ($(CONFIG_SUMMIT),y)
> > +MACHINE = mach-summit
> > endif
> >
> > Can make handle reassigning a variable?
>
> Sure.
>
> You could even do
>
> machine-y := mach-generic
> machine-$(CONFIG_SUMMIT) := mach-summit
> ...
> MACHINE := $(machine-y)
Cool. With a setup that clean I think I can break the multiple firmware
code out easily as well.
firmware-y := firmware-pcbios
firmware-$(CONFIG_LINUXBIOS) := firmware-linuxbios
...
FIRMWARE := $(firmware-y)
I had it broken out cleanly earlier, but everyone was concentrating
on other things and I just haven't been able to get back to that
stuff until this week. It will be a little tight coming in under
the wire with working code but we will see.
Unless someone has some objections...
Eric
next prev parent reply other threads:[~2002-10-14 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 20:41 Martin J. Bligh
2002-10-13 20:59 ` Greg KH
2002-10-13 21:06 ` Martin J. Bligh
2002-10-13 21:17 ` Greg KH
2002-10-13 21:31 ` Dave Jones
2002-10-13 22:15 ` Linus Torvalds
2002-10-14 2:02 ` Martin J. Bligh
2002-10-14 2:25 ` Greg KH
2002-10-14 2:49 ` Kai Germaschewski
2002-10-14 3:02 ` Greg KH
2002-10-14 5:46 ` Eric W. Biederman [this message]
2002-10-14 3:09 ` 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=m1adlhlgi7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®