From: Vojtech Pavlik <vojtech@suse.cz>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Dave Jones <davej@suse.de>, Martin Dalecki <martin@dalecki.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Actually hide x86 IDE chipsets on !CONFIG_X86
Date: Thu, 14 Mar 2002 19:41:01 +0100 [thread overview]
Message-ID: <20020314194101.B15318@ucw.cz> (raw)
In-Reply-To: <20020314165018.GE706@opus.bloom.county> <20020314181106.J19636@suse.de> <20020314172402.GG706@opus.bloom.county>
In-Reply-To: <20020314172402.GG706@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Mar 14, 2002 at 10:24:02AM -0700
On Thu, Mar 14, 2002 at 10:24:02AM -0700, Tom Rini wrote:
> On Thu, Mar 14, 2002 at 06:11:06PM +0100, Dave Jones wrote:
> > On Thu, Mar 14, 2002 at 09:50:18AM -0700, Tom Rini wrote:
> > > Hello. The following actually hides x86-specific drivers on
> > > !CONFIG_X86. The problem is that dep_bool '...' CONFIG_FOO $CONFIG_BAR
> > > doesn't have the desired effect if CONFIG_BAR isn't set.
> > >
> > > + if [ "$CONFIG_X86" = "y" ]; then
> > > + bool ' CMD640 chipset bugfix/support' CONFIG_BLK_DEV_CMD640
> > > + dep_bool ' CMD640 enhanced support' CONFIG_BLK_DEV_CMD640_ENHANCED $CONFIG_BLK_DEV_CMD640
> > > + fi
> >
> > I've a PCI card with one of these. It could in theory work on any arch
> > with a PCI slot.
>
> A 640 and not a 646?
Yes, exactly. I have one on a card as well.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-03-14 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 16:50 [PATCH] Actually hide x86 IDE chipsets on !CONFIG_X86 Tom Rini
2002-03-14 17:11 ` Dave Jones
2002-03-14 17:24 ` Tom Rini
2002-03-14 18:41 ` Vojtech Pavlik [this message]
2002-03-14 18:56 ` Tom Rini
2002-03-14 18:58 ` Dave Jones
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=20020314194101.B15318@ucw.cz \
--to=vojtech@suse.cz \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=trini@kernel.crashing.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 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.