From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Prasun Maiti <prasunmaiti87@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Dibyajyoti Ghosh <dibyajyotig@gmail.com>,
Ujjal Roy <royujjal@gmail.com>,
WiFi Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: wext: making deprecation more visible
Date: Tue, 07 Jun 2016 09:13:52 +0200 [thread overview]
Message-ID: <1465283632.2304.16.camel@sipsolutions.net> (raw)
In-Reply-To: <87porxlfqb.fsf_-_@purkki.adurom.net>
> I know we can't remove wext because of legacy applications but is
> there anything more we can do to make the users aware that wext is
> depreciated and really should be avoided? For example a onetime
> kernel warning? Or is that too spammy? Anything else?
The problem is that wext is in this weird hybrid state where it's
really deprecated if you can use nl80211, but you are required to use
wext if you can't use nl80211. Now, we disabled wext-for-cfg80211 by
default, but it's still there and could be used for some cases.
We probably should try to fix things, but I realize that code that
never gets tested [1].
Maybe we could print a message in the special cfg80211-wext case, which
has a special case in wext-core to avoid creating all those iw_handler
tables?
johannes
[1] and yeah - people move to nl80211 once told, so there's evidently
very little incentive to keep using wext, so in reality people don't
really seem to have applications that only use wext even with pure
cfg80211 drivers ...
next prev parent reply other threads:[~2016-06-07 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 7:40 [PATCH] wext: Fix 32 bit iwpriv compatibility issue with 64 bit Kernel Prasun Maiti
2016-05-31 10:25 ` Johannes Berg
2016-06-03 9:24 ` Prasun Maiti
2016-06-03 18:47 ` Johannes Berg
2016-06-04 4:50 ` wext: making deprecation more visible Kalle Valo
2016-06-07 7:13 ` Johannes Berg [this message]
2016-06-06 14:34 ` [PATCH] wext: Fix 32 bit iwpriv compatibility issue with 64 bit Kernel Prasun Maiti
2016-06-09 7:57 ` 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=1465283632.2304.16.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=dibyajyotig@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=prasunmaiti87@gmail.com \
--cc=royujjal@gmail.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).