From: Adrian Bunk <bunk@fs.tum.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Voyager subarchitecture (and other subarch updates) for 2.5.49
Date: Tue, 26 Nov 2002 00:00:12 +0100 [thread overview]
Message-ID: <20021125230011.GB24796@fs.tum.de> (raw)
In-Reply-To: <200211251625.gAPGPup02807@localhost.localdomain>
On Mon, Nov 25, 2002 at 10:25:56AM -0600, James Bottomley wrote:
> This patch adds
>...
> - Subarchitecture menu (Adrian Bunk)
>...
Thanks for adding it, just a note that this diff includes a version that
is different from the one I sent (that's no problem for me, you know
more about Voyager than I do).
> James
Content-Description: voyager-2.5.49.diff
>...
> --- a/arch/i386/Kconfig Mon Nov 25 10:17:13 2002
> +++ b/arch/i386/Kconfig Mon Nov 25 10:17:13 2002
>...
> config MCA
> bool "MCA support"
> - depends on !VISWS
> + depends on !VISWS && !VOYAGER
> help
> MicroChannel Architecture is found in some IBM PS/2 machines and
> laptops. It is a bus system similar to PCI or ISA. See
> <file:Documentation/mca.txt> (and especially the web page given
> there) before attempting to build an MCA bus kernel.
>
> +config MCA
> + depends on VOYAGER
> + default y if VOYAGER
>...
I'm not sure whether the latter works. My original patch included a
config MCA
bool
depends on VOYAGER
instead. This makes it more clear that it is actually what was called
define_bool in the old kconfig (even if it works a "default" entry in a
define_bool sounds really strange).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2002-11-25 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 16:25 James Bottomley
2002-11-25 23:00 ` Adrian Bunk [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=20021125230011.GB24796@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--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®