From: "Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>
To: akpm@osdl.org
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] HostAP: fix Kbuild warning
Date: Tue, 20 Sep 2005 20:48:54 +0200 [thread overview]
Message-ID: <20050920184853.15031.29856.stgit@zion.home.lan> (raw)
In-Reply-To: <20050920184810.15031.14521.stgit@zion.home.lan>
From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
The dependency on NET_RADIO is useless, because we select already it indirectly,
through IEEE80211.
The "recursive dependency" warning is actually IMHO partially wrong in this
context (we don't have a recursive dependency, but we *do* have recursion in the
code, for the way we recurse on "select" dependencies), but fixing it properly
doesn't seem easy (and I've not the time for this).
CC: Roman Zippel <zippel@linux-m68k.org>, <kbuild-devel@lists.sourceforge.net>
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
---
drivers/net/wireless/hostap/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/hostap/Kconfig b/drivers/net/wireless/hostap/Kconfig
--- a/drivers/net/wireless/hostap/Kconfig
+++ b/drivers/net/wireless/hostap/Kconfig
@@ -1,6 +1,6 @@
config HOSTAP
tristate "IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)"
- depends on NET_RADIO
+ #Dependency on NET_RADIO is implied by selecting IEEE80211 -> NET_RADIO.
select IEEE80211
select IEEE80211_CRYPT_WEP
---help---
prev parent reply other threads:[~2005-09-20 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 18:48 [PATCH 1/3] Kbuild: avoid indexing .git directory for tags/cscope/ Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:48 ` [PATCH 2/3] Kbuild: index asm-$(SUBARCH) headers for UML Paolo 'Blaisorblade' Giarrusso
2005-09-20 18:48 ` Paolo 'Blaisorblade' Giarrusso [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=20050920184853.15031.29856.stgit@zion.home.lan \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox