From: Jeff Garzik <jgarzik@pobox.com>
To: akpm@osdl.org
Cc: davem@davemloft.net, netdev@oss.sgi.com, bunk@stusta.de
Subject: Re: [patch 1/3] fix buggy IEEE80211_CRYPT_* selects
Date: Fri, 04 Mar 2005 12:33:19 -0500 [thread overview]
Message-ID: <42289BDF.1080409@pobox.com> (raw)
In-Reply-To: <200503041237.j24Cbb69026470@shell0.pdx.osdl.net>
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.
Jeff
next prev parent reply other threads:[~2005-03-04 17:33 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 [this message]
2005-03-04 22:10 ` Adrian Bunk
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=42289BDF.1080409@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--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 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.