From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH] schedule wext/rtnl for removal
Date: Thu, 01 Mar 2007 15:35:55 +0100 [thread overview]
Message-ID: <1172759755.11911.63.camel@johannes.berg> (raw)
Since wext is being replaced as fast as we can (it'll probably stick
around for legacy drivers though) and the wext/netlink stuff was never
really used, this schedules it for removal.
The removal schedule is tight but there are no users of the code, the
main user of the wext user interface are the wireless-tools, they only
have an alpha version using the netlink interface and even that is
incomplete.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
Documentation/feature-removal-schedule.txt | 12 ++++++++++++
1 file changed, 12 insertions(+)
--- linux-2.6.orig/Documentation/feature-removal-schedule.txt 2007-03-01 15:25:31.714246483 +0100
+++ linux-2.6/Documentation/feature-removal-schedule.txt 2007-03-01 15:32:23.904246483 +0100
@@ -304,3 +304,15 @@ Why: The code says it was obsolete when
Who: Richard Purdie <rpurdie@rpsys.net>
---------------------------
+
+What: Wireless extensions over netlink (CONFIG_NET_WIRELESS_RTNETLINK)
+When: with the merge of wireless-dev, 2.6.22 or later
+Why: The option/code is
+ * not enabled on most kernels
+ * not required by any userspace tools (except an experimental one,
+ and even there only for some parts, others use ioctl)
+ * pointless since wext is no longer evolving and the ioctl
+ interface needs to be kept
+Who: Johannes Berg <johannes@sipsolutions.net>
+
+---------------------------
next reply other threads:[~2007-03-01 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 14:35 Johannes Berg [this message]
[not found] <20070301153105.GC5806@tuxdriver.com>
2007-03-03 1:25 ` [PATCH] schedule wext/rtnl for removal Jeff Garzik
2007-03-03 1:25 ` 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=1172759755.11911.63.camel@johannes.berg \
--to=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 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.