linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] make ieee80211 invisible
Date: Tue, 14 Oct 2008 23:09:00 +0200	[thread overview]
Message-ID: <200810142309.00479.mb@bu3sch.de> (raw)
In-Reply-To: <1224006562.10113.47.camel@johannes.berg>

On Tuesday 14 October 2008 19:49:22 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.

I think in the long term we should also rename it to ipw-ieee80211
and move it into another directory like drivers/net/wireless/ipw-ieee80211.
This way it's a lot less confusing for new developers joining the wireless developers.

(Probably also rename the symbols. I'm not sure if it's worth it, however)

-- 
Greetings Michael.

  reply	other threads:[~2008-10-14 21:09 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 [this message]
2008-10-14 21:13   ` Johannes Berg
2008-10-15 17:37 ` reinette chatre
2008-10-15 17:49   ` Johannes Berg
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=200810142309.00479.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).