gpio calls don't need i/o barriers

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

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 0599a0c7c026174dce41b5a91f431f2919d95504..cff63befeb9a296b69ff91950dece03d574d279e 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -26,9 +26,7 @@ Who:  Hans Verkuil <hverkuil@xs4all.nl> and
 
 ---------------------------
 
-What:  /sys/devices/.../power/state
-       dev->power.power_state
-       dpm_runtime_{suspend,resume)()
+What:  dev->power.power_state
 When:  July 2007
 Why:   Broken design for runtime control over driver power states, confusing
        driver-internal runtime power management with:  mechanisms to support
@@ -41,14 +39,6 @@ Who: Pavel Machek <pavel@suse.cz>
 
 ---------------------------
 
-What:  RAW driver (CONFIG_RAW_DRIVER)
-When:  December 2005
-Why:   declared obsolete since kernel 2.6.3
-       O_DIRECT can be used instead
-Who:   Adrian Bunk <bunk@stusta.de>
-
----------------------------
-
 What:  old NCR53C9x driver
 When:  October 2007
 Why:   Replaced by the much better esp_scsi driver.  Actual low-level
@@ -119,13 +109,6 @@ 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:  Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
        (temporary transition config option provided until then)
        The transition config option will also be removed at the same time.
@@ -152,6 +135,15 @@ Who:       Greg Kroah-Hartman <gregkh@suse.de>
 
 ---------------------------
 
+What:  vm_ops.nopage
+When:  Soon, provided in-kernel callers have been converted
+Why:   This interface is replaced by vm_ops.fault, but it has been around
+       forever, is used by a lot of drivers, and doesn't cost much to
+       maintain.
+Who:   Nick Piggin <npiggin@suse.de>
+
+---------------------------
+
 What:  Interrupt only SA_* flags
 When:  September 2007
 Why:   The interrupt related SA_* flags are replaced by IRQF_* to move them
@@ -196,28 +188,6 @@ Who:   Adrian Bunk <bunk@stusta.de>
 
 ---------------------------
 
-What:  ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver
-When:  December 2006
-Why:   Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are
-       functionally very much similar. They talk to ACPI in same way. Only
-       difference between them is the way they do frequency transitions.
-       One uses MSRs and the other one uses IO ports. Functionaliy of
-       speedstep_centrino with ACPI hooks is now merged into acpi-cpufreq.
-       That means one common driver will support all Intel Enhanced Speedstep
-       capable CPUs. That means less confusion over name of
-       speedstep-centrino driver (with that driver supposed to be used on
-       non-centrino platforms). That means less duplication of code and
-       less maintenance effort and no possibility of these two drivers
-       going out of sync.
-       Current users of speedstep_centrino with ACPI hooks are requested to
-       switch over to acpi-cpufreq driver. speedstep-centrino will continue
-       to work using older non-ACPI static table based scheme even after this
-       date.
-
-Who:   Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
-
----------------------------
-
 What:  /sys/firmware/acpi/namespace
 When:  2.6.21
 Why:   The ACPI namespace is effectively the symbol list for
@@ -286,6 +256,14 @@ Who:       Jean Delvare <khali@linux-fr.org>
 
 ---------------------------
 
+What:  'time' kernel boot parameter
+When:  January 2008
+Why:   replaced by 'printk.time=<value>' so that printk timestamps can be
+       enabled or disabled as needed
+Who:   Randy Dunlap <randy.dunlap@oracle.com>
+
+---------------------------
+
 What:  drivers depending on OSS_OBSOLETE
 When:  options in 2.6.23, code in 2.6.25
 Why:   obsolete OSS drivers
@@ -326,3 +304,26 @@ Why:       Obsolete for multiple years now, NAT core provides the same behaviour.
 Who:   Patrick McHardy <kaber@trash.net>
 
 ---------------------------
+
+What: The arch/ppc and include/asm-ppc directories
+When: Jun 2008
+Why:  The arch/powerpc tree is the merged architecture for ppc32 and ppc64
+      platforms.  Currently there are efforts underway to port the remaining
+      arch/ppc platforms to the merged tree.  New submissions to the arch/ppc
+      tree have been frozen with the 2.6.22 kernel release and that tree will
+      remain in bug-fix only mode until its scheduled removal.  Platforms
+      that are not ported by June 2008 will be removed due to the lack of an
+      interested maintainer.
+Who:  linuxppc-dev@ozlabs.org
+
+---------------------------
+
+What:  mthca driver's MSI support
+When:  January 2008
+Files: drivers/infiniband/hw/mthca/*.[ch]
+Why:   All mthca hardware also supports MSI-X, which provides
+       strictly more functionality than MSI.  So there is no point in
+       having both MSI-X and MSI support in the driver.
+Who:   Roland Dreier <rolandd@cisco.com>
+
+---------------------------