ub: Bind to first endpoint, not to last

[linux-2.6] / Documentation / feature-removal-schedule.txt

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 9817b60e70a36526a597e16f3572871641062d09..ec0b4843b1cb2f41c79adf787423d4afaad14905 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -134,15 +134,6 @@ Who:       Arjan van de Ven <arjan@linux.intel.com>
 
 ---------------------------
 
-What:  mount/umount uevents
-When:  February 2007
-Why:   These events are not correct, and do not properly let userspace know
-       when a file system has been mounted or unmounted.  Userspace should
-       poll the /proc/mounts file instead to detect this properly.
-Who:   Greg Kroah-Hartman <gregkh@suse.de>
-
----------------------------
-
 What:  USB driver API moves to EXPORT_SYMBOL_GPL
 When:  February 2008
 Files: include/linux/usb.h, drivers/usb/core/driver.c
@@ -285,18 +276,6 @@ 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>
-
----------------------------
-
 What:  i8xx_tco watchdog driver
 When:  in 2.6.22
 Why:   the i8xx_tco watchdog driver has been replaced by the iTCO_wdt
@@ -304,3 +283,22 @@ Why:       the i8xx_tco watchdog driver has been replaced by the iTCO_wdt
 Who:   Wim Van Sebroeck <wim@iguana.be>
 
 ---------------------------
+
+What:  Multipath cached routing support in ipv4
+When:  in 2.6.23
+Why:   Code was merged, then submitter immediately disappeared leaving
+       us with no maintainer and lots of bugs.  The code should not have
+       been merged in the first place, and many aspects of it's
+       implementation are blocking more critical core networking
+       development.  It's marked EXPERIMENTAL and no distribution
+       enables it because it cause obscure crashes due to unfixable bugs
+       (interfaces don't return errors so memory allocation can't be
+       handled, calling contexts of these interfaces make handling
+       errors impossible too because they get called after we've
+       totally commited to creating a route object, for example).
+       This problem has existed for years and no forward progress
+       has ever been made, and nobody steps up to try and salvage
+       this code, so we're going to finally just get rid of it.
+Who:   David S. Miller <davem@davemloft.net>
+
+---------------------------