Merge branch 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6

[pandora-kernel.git] / Documentation / feature-removal-schedule.txt

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 87851ef..611acc3 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -6,6 +6,21 @@ be removed from this file.
 
 ---------------------------
 
+What:  /sys/devices/.../power/state
+       dev->power.power_state
+       dpm_runtime_{suspend,resume)()
+When:  July 2007
+Why:   Broken design for runtime control over driver power states, confusing
+       driver-internal runtime power management with:  mechanisms to support
+       system-wide sleep state transitions; event codes that distinguish
+       different phases of swsusp "sleep" transitions; and userspace policy
+       inputs.  This framework was never widely used, and most attempts to
+       use it were broken.  Drivers should instead be exposing domain-specific
+       interfaces either to kernel or to userspace.
+Who:   Pavel Machek <pavel@suse.cz>
+
+---------------------------
+
 What:  RAW driver (CONFIG_RAW_DRIVER)
 When:  December 2005
 Why:   declared obsolete since kernel 2.6.3
@@ -120,6 +135,13 @@ Who:    Adrian Bunk <bunk@stusta.de>
 
 ---------------------------
 
+What:  drivers depending on OSS_OBSOLETE_DRIVER
+When:  options in 2.6.20, code in 2.6.22
+Why:   OSS drivers with ALSA replacements
+Who:   Adrian Bunk <bunk@stusta.de>
+
+---------------------------
+
 What:  pci_module_init(driver)
 When:  January 2007
 Why:   Is replaced by pci_register_driver(pci_driver).
@@ -274,3 +296,28 @@ Why:       The deferred output hooks are a layering violation causing unusual
 Who:   Patrick McHardy <kaber@trash.net>
 
 ---------------------------
+
+What:  frame diverter
+When:  November 2006
+Why:   The frame diverter is included in most distribution kernels, but is
+       broken. It does not correctly handle many things:
+       - IPV6
+       - non-linear skb's
+       - network device RCU on removal
+       - input frames not correctly checked for protocol errors
+       It also adds allocation overhead even if not enabled.
+       It is not clear if anyone is still using it.
+Who:   Stephen Hemminger <shemminger@osdl.org>
+
+---------------------------
+
+
+What:  PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
+When:  Oktober 2008
+Why:   The stacking of class devices makes these values misleading and
+       inconsistent.
+       Class devices should not carry any of these properties, and bus
+       devices have SUBSYTEM and DRIVER as a replacement.
+Who:   Kay Sievers <kay.sievers@suse.de>
+
+---------------------------