From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jgarzik@pobox.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: akpm@osdl.org, davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [patch 1/3] fix buggy IEEE80211_CRYPT_* selects
Date: Fri, 4 Mar 2005 23:10:15 +0100 [thread overview]
Message-ID: <20050304221014.GJ3327@stusta.de> (raw)
In-Reply-To: <42289BDF.1080409@pobox.com>
On Fri, Mar 04, 2005 at 12:33:19PM -0500, Jeff Garzik wrote:
> akpm@osdl.org wrote:
> >From: Adrian Bunk <bunk@stusta.de>
> >
> >Some of the options that needlessly wrote in their help text which options
> >they do select (patch already sent) didn't obey the most important rule of
> >select
> >
> > If you select something, you have to ensure that the dependencies
> > of what you do select are fulfilled.
>
> >diff -puN net/ieee80211/Kconfig~fix-buggy-ieee80211_crypt_-selects
> >net/ieee80211/Kconfig
> >--- 25/net/ieee80211/Kconfig~fix-buggy-ieee80211_crypt_-selects 2005-02-28
> >14:49:54.000000000 -0800
> >+++ 25-akpm/net/ieee80211/Kconfig 2005-02-28 14:49:54.000000000 -0800
> >@@ -44,6 +44,7 @@ config IEEE80211_CRYPT_WEP
> > config IEEE80211_CRYPT_CCMP
> > tristate "IEEE 802.11i CCMP support"
> > depends on IEEE80211
> >+ select CRYPTO
> > select CRYPTO_AES
> > ---help---
> > Include software based cipher suites in support of IEEE 802.11i
> >@@ -56,6 +57,7 @@ config IEEE80211_CRYPT_CCMP
> > config IEEE80211_CRYPT_TKIP
> > tristate "IEEE 802.11i TKIP encryption"
> > depends on IEEE80211
> >+ select CRYPTO
> > select CRYPTO_MICHAEL_MIC
> > ---help---
>
>
> You are resending the old patch that is incorrect. We don't need
> multiple selects, CRYPTO_AES and CRYPTO_MICHAEL_MIC should pull things in.
As I already said, this implies that options like CRYPTO_AES and
CRYPTO_MICHAEL_MIC can no longer depend on CRYPTO.
It's possible to change the crypto options in a way that CRYPTO is
selected as required but no longer directly selectable (and I could send
such a patch), but that's a decision of the crypto maintainers.
> Jeff
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
next prev parent reply other threads:[~2005-03-04 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 12:37 [patch 1/3] fix buggy IEEE80211_CRYPT_* selects akpm
2005-03-04 17:33 ` Jeff Garzik
2005-03-04 22:10 ` Adrian Bunk [this message]
2005-03-04 22:21 ` Jeff Garzik
2005-03-04 23:07 ` Adrian Bunk
2005-03-06 9:09 ` Herbert Xu
2005-03-06 18:00 ` Jeff Garzik
2005-03-06 19:10 ` Adrian Bunk
2005-03-06 19:13 ` Jeff Garzik
2005-03-06 21:09 ` Herbert Xu
2005-03-09 20:21 ` Jeff Garzik
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=20050304221014.GJ3327@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).