[PATCH] schedule wext/rtnl for removal

[PATCH] schedule wext/rtnl for removal

[Johannes Berg]

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>
+
+---------------------------

Re: [PATCH] schedule wext/rtnl for removal

[Jeff Garzik]

John W. Linville wrote:
> From: Johannes Berg <johannes@sipsolutions.net>
> 
> 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>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> Which you consider applying this feature-removal-schedule.txt patch
> in the current (i.e. pre-2.6.21) timeframe?
> 
>  Documentation/feature-removal-schedule.txt |   12 ++++++++++++
>  1 file changed, 12 insertions(+)

When you send this sort of stuff, spam as many lists as reasonable.

The removal of a recently-added userspace ABI is an unusual event, and 
IMO needs discussing.

Re: [PATCH] schedule wext/rtnl for removal

[Jeff Garzik]

John W. Linville wrote:
> From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> 
> 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-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> Signed-off-by: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> ---
> Which you consider applying this feature-removal-schedule.txt patch
> in the current (i.e. pre-2.6.21) timeframe?
> 
>  Documentation/feature-removal-schedule.txt |   12 ++++++++++++
>  1 file changed, 12 insertions(+)

When you send this sort of stuff, spam as many lists as reasonable.

The removal of a recently-added userspace ABI is an unusual event, and 
IMO needs discussing.