From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-arch@vger.kernel.org
Subject: Re: [patch 1/5] Kconfig: refine some depend statements.
Date: Tue, 05 Sep 2006 19:17:29 +0200 [thread overview]
Message-ID: <1157476649.13223.3.camel@localhost> (raw)
In-Reply-To: <20060905165032.GI2558@parisc-linux.org>
On Tue, 2006-09-05 at 10:50 -0600, Matthew Wilcox wrote:
> > menu "IEEE 1394 (FireWire) support"
> > + depends on PCI || BROKEN
>
> Why the || BROKEN?
That was the conclusion last time as far as I can remember. The essence
of the statement was that firewire works for PCI, any other use is
broken. We can change that to "PCI" only if that is ok with everbody.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2006-09-05 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 16:33 [patch 1/5] Kconfig: refine some depend statements Martin Schwidefsky
2006-09-05 16:50 ` Matthew Wilcox
2006-09-05 17:17 ` Martin Schwidefsky [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=1157476649.13223.3.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
/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