From: Sam Ravnborg <sam@ravnborg.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
"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: Thu, 21 Nov 2002 20:15:06 +0100 [thread overview]
Message-ID: <20021121191506.GA2007@mars.ravnborg.org> (raw)
In-Reply-To: <1037904954.7576.62.camel@w-jstultz2.beaverton.ibm.com>
On Thu, Nov 21, 2002 at 10:55:54AM -0800, john stultz wrote:
> 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.
If we are going to extend the concept of machines for i386 we should
add a default CONFIG option for the generic case.
Then we could do something like:
core-$(CONFIG_MACH_I386GENERIC) += arch/i386/mach-generic
core-$(CONFIG_MACH_VISWS) += arch/i386/mach-visws
core-$(CONFIG_MACH_SUMMIT) += arch/i386/mach-generic
mflags-$(CONFIG_MACH_VISWS) := asm/mach-visws
mflags-$(CONFIG_MACH_SUMMIT) := asm/mach-summit
mflags-y += asm/mach-generic
AFLAGS += $(mflags-y)
CFLAGS += $(mflags-y)
There is something similar done for arm in newest kernel.
Sam
next prev parent reply other threads:[~2002-11-21 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 0:00 [RFC] [PATCH] subarch cleanup 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
2002-11-21 19:15 ` Sam Ravnborg [this message]
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=20021121191506.GA2007@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=johnstul@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.