aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt26
1 files changed, 22 insertions, 4 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index d05e6243b4df..a9941544ed8e 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -26,9 +26,7 @@ Who: Hans Verkuil <hverkuil@xs4all.nl> and
26 26
27--------------------------- 27---------------------------
28 28
29What: /sys/devices/.../power/state 29What: dev->power.power_state
30 dev->power.power_state
31 dpm_runtime_{suspend,resume)()
32When: July 2007 30When: July 2007
33Why: Broken design for runtime control over driver power states, confusing 31Why: Broken design for runtime control over driver power states, confusing
34 driver-internal runtime power management with: mechanisms to support 32 driver-internal runtime power management with: mechanisms to support
@@ -53,6 +51,7 @@ Who: David Miller <davem@davemloft.net>
53What: Video4Linux API 1 ioctls and video_decoder.h from Video devices. 51What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
54When: December 2006 52When: December 2006
55Files: include/linux/video_decoder.h 53Files: include/linux/video_decoder.h
54Check: include/linux/video_decoder.h
56Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6 55Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
57 series. The old API have lots of drawbacks and don't provide enough 56 series. The old API have lots of drawbacks and don't provide enough
58 means to work with all video and audio standards. The newer API is 57 means to work with all video and audio standards. The newer API is
@@ -86,7 +85,7 @@ Who: Dominik Brodowski <linux@brodo.de>
86What: remove EXPORT_SYMBOL(kernel_thread) 85What: remove EXPORT_SYMBOL(kernel_thread)
87When: August 2006 86When: August 2006
88Files: arch/*/kernel/*_ksyms.c 87Files: arch/*/kernel/*_ksyms.c
89Funcs: kernel_thread 88Check: kernel_thread
90Why: kernel_thread is a low-level implementation detail. Drivers should 89Why: kernel_thread is a low-level implementation detail. Drivers should
91 use the <linux/kthread.h> API instead which shields them from 90 use the <linux/kthread.h> API instead which shields them from
92 implementation details and provides a higherlevel interface that 91 implementation details and provides a higherlevel interface that
@@ -137,6 +136,15 @@ Who: Greg Kroah-Hartman <gregkh@suse.de>
137 136
138--------------------------- 137---------------------------
139 138
139What: vm_ops.nopage
140When: Soon, provided in-kernel callers have been converted
141Why: This interface is replaced by vm_ops.fault, but it has been around
142 forever, is used by a lot of drivers, and doesn't cost much to
143 maintain.
144Who: Nick Piggin <npiggin@suse.de>
145
146---------------------------
147
140What: Interrupt only SA_* flags 148What: Interrupt only SA_* flags
141When: September 2007 149When: September 2007
142Why: The interrupt related SA_* flags are replaced by IRQF_* to move them 150Why: The interrupt related SA_* flags are replaced by IRQF_* to move them
@@ -310,3 +318,13 @@ Why: The arch/powerpc tree is the merged architecture for ppc32 and ppc64
310Who: linuxppc-dev@ozlabs.org 318Who: linuxppc-dev@ozlabs.org
311 319
312--------------------------- 320---------------------------
321
322What: mthca driver's MSI support
323When: January 2008
324Files: drivers/infiniband/hw/mthca/*.[ch]
325Why: All mthca hardware also supports MSI-X, which provides
326 strictly more functionality than MSI. So there is no point in
327 having both MSI-X and MSI support in the driver.
328Who: Roland Dreier <rolandd@cisco.com>
329
330---------------------------