From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] make ieee80211 invisible
Date: Wed, 15 Oct 2008 19:49:01 +0200 [thread overview]
Message-ID: <1224092941.735.23.camel@johannes.berg> (raw)
In-Reply-To: <1224092268.19219.7.camel@rc-desk>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Wed, 2008-10-15 at 10:37 -0700, reinette chatre wrote:
> On Tue, 2008-10-14 at 19:49 +0200, Johannes Berg wrote:
> >
> > This makes CONFIG_IEEE80211 invisible. The drivers that require it
> > (ipw2100, ipw2200, hostap) select it, and everybody else really
> > shouldn't even think about using it. Also, since there really is
> > no point in compiling anything without crypto support these days,
> > remove the crypto options and just enable them, leaving only the
> > debugging option which only shows up when a driver is select that
> > requires it. This makes it hard to enable, but most people wouldn't
> > want to anyway.
> >
> > Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> > ---
>
> Very good idea. Not sure if you need an ack from us for this, but you
> have mine in case you do.
>
> Acked-by: Reinette Chatre <reinette.chatre@intel.com>
Any pair of eyeballs is welcome either way! Thanks for looking.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-15 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 17:49 [RFC] make ieee80211 invisible Johannes Berg
2008-10-14 21:09 ` Michael Buesch
2008-10-14 21:13 ` Johannes Berg
2008-10-15 17:37 ` reinette chatre
2008-10-15 17:49 ` Johannes Berg [this message]
2008-10-21 10:46 ` Johannes Berg
2008-10-21 17:38 ` John W. Linville
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=1224092941.735.23.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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.