IB/mthca: Fix IB_QP_ACCESS_FLAGS handling.
[linux-block.git] / Documentation / feature-removal-schedule.txt
CommitLineData
1da177e4
LT
1The following is a list of files and features that are going to be
2removed in the kernel source tree. Every entry should contain what
3exactly is going away, why it is happening, and who is going to be doing
4the work. When the feature is removed from the kernel, it should also
5be removed from this file.
6
7---------------------------
8
9What: devfs
10When: July 2005
11Files: fs/devfs/*, include/linux/devfs_fs*.h and assorted devfs
12 function calls throughout the kernel tree
13Why: It has been unmaintained for a number of years, has unfixable
14 races, contains a naming policy within the kernel that is
15 against the LSB, and can be replaced by using udev.
16Who: Greg Kroah-Hartman <greg@kroah.com>
17
18---------------------------
19
98e7f294
AB
20What: RAW driver (CONFIG_RAW_DRIVER)
21When: December 2005
22Why: declared obsolete since kernel 2.6.3
23 O_DIRECT can be used instead
24Who: Adrian Bunk <bunk@stusta.de>
25
26---------------------------
27
cecd1ca0
AB
28What: drivers depending on OBSOLETE_OSS_DRIVER
29When: January 2006
30Why: OSS drivers with ALSA replacements
31Who: Adrian Bunk <bunk@stusta.de>
32
33---------------------------
34
66cf8f14
PM
35What: RCU API moves to EXPORT_SYMBOL_GPL
36When: April 2006
37Files: include/linux/rcupdate.h, kernel/rcupdate.c
38Why: Outside of Linux, the only implementations of anything even
39 vaguely resembling RCU that I am aware of are in DYNIX/ptx,
40 VM/XA, Tornado, and K42. I do not expect anyone to port binary
41 drivers or kernel modules from any of these, since the first two
42 are owned by IBM and the last two are open-source research OSes.
43 So these will move to GPL after a grace period to allow
44 people, who might be using implementations that I am not aware
45 of, to adjust to this upcoming change.
46Who: Paul E. McKenney <paulmck@us.ibm.com>
a1446c7f
JM
47
48---------------------------
49
50What: IEEE1394 Audio and Music Data Transmission Protocol driver,
51 Connection Management Procedures driver
52When: November 2005
53Files: drivers/ieee1394/{amdtp,cmp}*
54Why: These are incomplete, have never worked, and are better implemented
55 in userland via raw1394 (see http://freebob.sourceforge.net/ for
56 example.)
57Who: Jody McIntyre <scjody@steamballoon.com>
58
59---------------------------
60
61What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN
62When: November 2005
63Why: Deprecated in favour of the new ioctl-based rawiso interface, which is
64 more efficient. You should really be using libraw1394 for raw1394
65 access anyway.
66Who: Jody McIntyre <scjody@steamballoon.com>
937df8df
GC
67
68---------------------------
69
875c296b
MCC
70What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
71When: July 2006
72Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
73 series. The old API have lots of drawbacks and don't provide enough
74 means to work with all video and audio standards. The newer API is
75 already available on the main drivers and should be used instead.
76 Newer drivers should use v4l_compat_translate_ioctl function to handle
77 old calls, replacing to newer ones.
78 Decoder iocts are using internally to allow video drivers to
79 communicate with video decoders. This should also be improved to allow
80 V4L2 calls being translated into compatible internal ioctls.
81Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
82
83---------------------------
84
937df8df
GC
85What: i2c sysfs name change: in1_ref, vid deprecated in favour of cpu0_vid
86When: November 2005
87Files: drivers/i2c/chips/adm1025.c, drivers/i2c/chips/adm1026.c
88Why: Match the other drivers' name for the same function, duplicate names
89 will be available until removal of old names.
90Who: Grant Coady <gcoady@gmail.com>
91
bf45d9b0
DB
92---------------------------
93
dfed0449
AB
94What: remove EXPORT_SYMBOL(panic_timeout)
95When: April 2006
96Files: kernel/panic.c
97Why: No modular usage in the kernel.
98Who: Adrian Bunk <bunk@stusta.de>
99
100---------------------------
101
24622efd
AB
102What: remove EXPORT_SYMBOL(insert_resource)
103When: April 2006
104Files: kernel/resource.c
105Why: No modular usage in the kernel.
106Who: Adrian Bunk <bunk@stusta.de>
107
108---------------------------
109
bf45d9b0
DB
110What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
111When: November 2005
112Files: drivers/pcmcia/: pcmcia_ioctl.c
113Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a
114 normal hotpluggable bus, and with it using the default kernel
115 infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA
116 control ioctl needed by cardmgr and cardctl from pcmcia-cs is
117 unnecessary, and makes further cleanups and integration of the
118 PCMCIA subsystem into the Linux kernel device driver model more
119 difficult. The features provided by cardmgr and cardctl are either
120 handled by the kernel itself now or are available in the new
121 pcmciautils package available at
122 http://kernel.org/pub/linux/utils/kernel/pcmcia/
123Who: Dominik Brodowski <linux@brodo.de>
7af4cc3f
HW
124
125---------------------------
126
127What: ip_queue and ip6_queue (old ipv4-only and ipv6-only netfilter queue)
128When: December 2005
129Why: This interface has been obsoleted by the new layer3-independent
130 "nfnetlink_queue". The Kernel interface is compatible, so the old
131 ip[6]tables "QUEUE" targets still work and will transparently handle
132 all packets into nfnetlink queue number 0. Userspace users will have
133 to link against API-compatible library on top of libnfnetlink_queue
134 instead of the current 'libipq'.
135Who: Harald Welte <laforge@netfilter.org>
49705b77
CH
136
137---------------------------
138
139What: EXPORT_SYMBOL(lookup_hash)
140When: January 2006
141Why: Too low-level interface. Use lookup_one_len or lookup_create instead.
142Who: Christoph Hellwig <hch@lst.de>
e8a00334
N
143
144---------------------------
145
146What: START_ARRAY ioctl for md
147When: July 2006
148Files: drivers/md/md.c
149Why: Not reliable by design - can fail when most needed.
150 Alternatives exist
151Who: NeilBrown <neilb@suse.de>
e0c9b797
RB
152
153---------------------------
154
155What: au1x00_uart driver
156When: January 2006
157Why: The 8250 serial driver now has the ability to deal with the differences
158 between the standard 8250 family of UARTs and their slightly strange
159 brother on Alchemy SOCs. The loss of features is not considered an
160 issue.
161Who: Ralf Baechle <ralf@linux-mips.org>