From: Kalle Valo <kvalo@adurom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: deprecate CFG80211_WEXT
Date: Wed, 09 Nov 2011 09:49:54 +0200 [thread overview]
Message-ID: <87ehxhag65.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1320781153.24797.41.camel@jlt3.sipsolutions.net> (Johannes Berg's message of "Tue\, 08 Nov 2011 20\:39\:13 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> Almost all wireless tools have transitioned to
> or at least added compatibility with nl80211 so
> there's no real need for CONFIG_CFG80211_WEXT
> any more. Mark it for removal, and also change
> the default to not be enabled.
Maybe CC lkml for more visibility?
--
Kalle Valo
next prev parent reply other threads:[~2011-11-09 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 19:39 [PATCH] cfg80211: deprecate CFG80211_WEXT Johannes Berg
2011-11-09 7:49 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-04 11:51 Johannes Berg
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=87ehxhag65.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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