From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
akpm@linux-foundation.org, linville@tuxdriver.com
Subject: Re: [PATCH 7/8] Kconfig: silicon backplane dependency.
Date: Mon, 23 Apr 2007 13:27:56 +0200 [thread overview]
Message-ID: <1177327676.5984.12.camel@localhost> (raw)
In-Reply-To: <200704231322.36970.arnd@arndb.de>
On Mon, 2007-04-23 at 13:22 +0200, Arnd Bergmann wrote:
> > The current Kconfig code does not check all select statements if they
> > can be enabled before allowing the config option that does the select.
> > So the rule for using select statements is that the depends line of the
> > config option that selects another config option needs to be at least as
> > restrictive as the depends line of the selected option. Hence I'll add
> > the HAS_IOMEM depends to B44 as well. Okay ?
>
> Isn't B44 already behind a WIRELESS or IEEE80211 or similar option that
> can't be selected on s390?
No, the option can be found in drivers/net/Kconfig under menu "Ethernet
(10 or 100Mbit)".
--
blue skies, IBM Deutschland Entwicklung GmbH
Martin Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Martin Schwidefsky Sitz der Gesellschaft: Böblingen
Linux on zSeries Registergericht: Amtsgericht Stuttgart,
Development HRB 243294
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2007-04-23 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 11:35 [PATCH 7/8] Kconfig: silicon backplane dependency Martin Schwidefsky
2007-04-20 20:45 ` Michael Buesch
2007-04-21 6:28 ` Martin Schwidefsky
2007-04-21 23:19 ` Arnd Bergmann
2007-04-22 7:53 ` Martin Schwidefsky
2007-04-22 9:46 ` Michael Buesch
2007-04-23 11:16 ` Martin Schwidefsky
2007-04-23 11:22 ` Arnd Bergmann
2007-04-23 11:27 ` Martin Schwidefsky [this message]
2007-04-23 11:48 ` Arnd Bergmann
2007-04-23 14:37 ` Michael Buesch
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=1177327676.5984.12.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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