blob: d6f5255ca54780f2aa8982445a15809a31ccd90c [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001The 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
Luis R. Rodriguez4d8cd262009-09-08 12:09:47 -07009What: PRISM54
10When: 2.6.34
11
12Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the
13 prism54 wireless driver. After Intersil stopped selling these
14 devices in preference for the newer more flexible SoftMAC devices
15 a SoftMAC device driver was required and prism54 did not support
16 them. The p54pci driver now exists and has been present in the kernel for
17 a while. This driver supports both SoftMAC devices and FullMAC devices.
18 The main difference between these devices was the amount of memory which
19 could be used for the firmware. The SoftMAC devices support a smaller
20 amount of memory. Because of this the SoftMAC firmware fits into FullMAC
21 devices's memory. p54pci supports not only PCI / Cardbus but also USB
22 and SPI. Since p54pci supports all devices prism54 supports
23 you will have a conflict. I'm not quite sure how distributions are
24 handling this conflict right now. prism54 was kept around due to
25 claims users may experience issues when using the SoftMAC driver.
26 Time has passed users have not reported issues. If you use prism54
27 and for whatever reason you cannot use p54pci please let us know!
28 E-mail us at: linux-wireless@vger.kernel.org
29
30 For more information see the p54 wiki page:
31
32 http://wireless.kernel.org/en/users/Drivers/p54
33
34Who: Luis R. Rodriguez <lrodriguez@atheros.com>
35
36---------------------------
37
Christian Lamparterf4562282011-02-09 22:13:11 +010038What: AR9170USB
39When: 2.6.40
40
41Why: This driver is deprecated and the firmware is no longer
42 maintained. The replacement driver "carl9170" has been
43 around for a while, so the devices are still supported.
44
45Who: Christian Lamparter <chunkeey@googlemail.com>
46
47---------------------------
48
Robin Getz9d9b8fb02009-06-17 16:25:54 -070049What: IRQF_SAMPLE_RANDOM
50Check: IRQF_SAMPLE_RANDOM
51When: July 2009
52
53Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy
54 sources in the kernel's current entropy model. To resolve this, every
55 input point to the kernel's entropy pool needs to better document the
56 type of entropy source it actually is. This will be replaced with
57 additional add_*_randomness functions in drivers/char/random.c
58
59Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com>
60
61---------------------------
62
Jiri Slabyb694e522010-01-27 23:47:50 +010063What: Deprecated snapshot ioctls
64When: 2.6.36
65
66Why: The ioctls in kernel/power/user.c were marked as deprecated long time
67 ago. Now they notify users about that so that they need to replace
68 their userspace. After some more time, remove them completely.
69
70Who: Jiri Slaby <jirislaby@gmail.com>
71
72---------------------------
73
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -040074What: The ieee80211_regdom module parameter
Luis R. Rodriguez8a5117d2009-03-24 21:21:07 -040075When: March 2010 / desktop catchup
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -040076
77Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code,
78 and currently serves as an option for users to define an
79 ISO / IEC 3166 alpha2 code for the country they are currently
80 present in. Although there are userspace API replacements for this
81 through nl80211 distributions haven't yet caught up with implementing
82 decent alternatives through standard GUIs. Although available as an
83 option through iw or wpa_supplicant its just a matter of time before
84 distributions pick up good GUI options for this. The ideal solution
85 would actually consist of intelligent designs which would do this for
86 the user automatically even when travelling through different countries.
87 Until then we leave this module parameter as a compromise.
88
89 When userspace improves with reasonable widely-available alternatives for
90 this we will no longer need this module parameter. This entry hopes that
91 by the super-futuristically looking date of "March 2010" we will have
92 such replacements widely available.
93
94Who: Luis R. Rodriguez <lrodriguez@atheros.com>
95
96---------------------------
97
Alan Stern471d0552007-07-12 16:55:07 -040098What: dev->power.power_state
Pavel Machek1ebfd792006-08-30 13:50:27 -070099When: July 2007
100Why: Broken design for runtime control over driver power states, confusing
101 driver-internal runtime power management with: mechanisms to support
102 system-wide sleep state transitions; event codes that distinguish
103 different phases of swsusp "sleep" transitions; and userspace policy
104 inputs. This framework was never widely used, and most attempts to
105 use it were broken. Drivers should instead be exposing domain-specific
106 interfaces either to kernel or to userspace.
Pavel Macheka2531292010-07-18 14:27:13 +0200107Who: Pavel Machek <pavel@ucw.cz>
Pavel Machek1ebfd792006-08-30 13:50:27 -0700108
109---------------------------
110
Mauro Carvalho Chehab7af97ef2010-09-30 08:25:42 -0300111What: Video4Linux obsolete drivers using V4L1 API
Hans Verkuil439105b2010-12-25 07:46:56 -0300112When: kernel 2.6.39
113Files: drivers/staging/se401/* drivers/staging/usbvideo/*
114Check: drivers/staging/se401/se401.c drivers/staging/usbvideo/usbvideo.c
Mauro Carvalho Chehab7af97ef2010-09-30 08:25:42 -0300115Why: There are some drivers still using V4L1 API, despite all efforts we've done
116 to migrate. Those drivers are for obsolete hardware that the old maintainer
117 didn't care (or not have the hardware anymore), and that no other developer
118 could find any hardware to buy. They probably have no practical usage today,
119 and people with such old hardware could probably keep using an older version
Hans Verkuil439105b2010-12-25 07:46:56 -0300120 of the kernel. Those drivers will be moved to staging on 2.6.38 and, if nobody
121 cares enough to port and test them with V4L2 API, they'll be removed on 2.6.39.
Mauro Carvalho Chehab7af97ef2010-09-30 08:25:42 -0300122Who: Mauro Carvalho Chehab <mchehab@infradead.org>
123
124---------------------------
125
Mauro Carvalho Chehab10357582010-12-27 11:14:52 -0300126What: Video4Linux: Remove obsolete ioctl's
127When: kernel 2.6.39
128Files: include/media/videodev2.h
129Why: Some ioctl's were defined wrong on 2.6.2 and 2.6.6, using the wrong
130 type of R/W arguments. They were fixed, but the old ioctl names are
131 still there, maintained to avoid breaking binary compatibility:
132 #define VIDIOC_OVERLAY_OLD _IOWR('V', 14, int)
133 #define VIDIOC_S_PARM_OLD _IOW('V', 22, struct v4l2_streamparm)
134 #define VIDIOC_S_CTRL_OLD _IOW('V', 28, struct v4l2_control)
135 #define VIDIOC_G_AUDIO_OLD _IOWR('V', 33, struct v4l2_audio)
136 #define VIDIOC_G_AUDOUT_OLD _IOWR('V', 49, struct v4l2_audioout)
137 #define VIDIOC_CROPCAP_OLD _IOR('V', 58, struct v4l2_cropcap)
138 There's no sense on preserving those forever, as it is very doubtful
139 that someone would try to use a such old binary with a modern kernel.
140 Removing them will allow us to remove some magic done at the V4L ioctl
141 handler.
142
143Who: Mauro Carvalho Chehab <mchehab@infradead.org>
144
145---------------------------
146
Eric W. Biederman7058cb02007-10-18 03:05:58 -0700147What: sys_sysctl
148When: September 2010
149Option: CONFIG_SYSCTL_SYSCALL
150Why: The same information is available in a more convenient from
151 /proc/sys, and none of the sysctl variables appear to be
152 important performance wise.
153
154 Binary sysctls are a long standing source of subtle kernel
155 bugs and security issues.
156
157 When I looked several months ago all I could find after
158 searching several distributions were 5 user space programs and
159 glibc (which falls back to /proc/sys) using this syscall.
160
161 The man page for sysctl(2) documents it as unusable for user
162 space programs.
163
164 sysctl(2) is not generally ABI compatible to a 32bit user
165 space application on a 64bit and a 32bit kernel.
166
167 For the last several months the policy has been no new binary
168 sysctls and no one has put forward an argument to use them.
169
170 Binary sysctls issues seem to keep happening appearing so
171 properly deprecating them (with a warning to user space) and a
172 2 year grace warning period will mean eventually we can kill
173 them and end the pain.
174
175 In the mean time individual binary sysctls can be dealt with
176 in a piecewise fashion.
177
178Who: Eric Biederman <ebiederm@xmission.com>
179
180---------------------------
181
David Rientjes51b1bd22010-08-09 17:19:47 -0700182What: /proc/<pid>/oom_adj
183When: August 2012
184Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's
185 badness heuristic used to determine which task to kill when the kernel
186 is out of memory.
187
188 The badness heuristic has since been rewritten since the introduction of
189 this tunable such that its meaning is deprecated. The value was
190 implemented as a bitshift on a score generated by the badness()
191 function that did not have any precise units of measure. With the
192 rewrite, the score is given as a proportion of available memory to the
193 task allocating pages, so using a bitshift which grows the score
194 exponentially is, thus, impossible to tune with fine granularity.
195
196 A much more powerful interface, /proc/<pid>/oom_score_adj, was
197 introduced with the oom killer rewrite that allows users to increase or
198 decrease the badness() score linearly. This interface will replace
199 /proc/<pid>/oom_adj.
200
201 A warning will be emitted to the kernel log if an application uses this
202 deprecated interface. After it is printed once, future warnings will be
203 suppressed until the kernel is rebooted.
204
205---------------------------
206
Andres Salomoncf8e9082011-01-12 17:00:12 -0800207What: CS5535/CS5536 obsolete GPIO driver
208When: June 2011
209Files: drivers/staging/cs5535_gpio/*
210Check: drivers/staging/cs5535_gpio/cs5535_gpio.c
211Why: A newer driver replaces this; it is drivers/gpio/cs5535-gpio.c, and
212 integrates with the Linux GPIO subsystem. The old driver has been
213 moved to staging, and will be removed altogether around 2.6.40.
214 Please test the new driver, and ensure that the functionality you
215 need and any bugfixes from the old driver are available in the new
216 one.
217Who: Andres Salomon <dilinger@queued.net>
218
219--------------------------
220
Christoph Hellwigac515892006-03-24 03:18:22 -0800221What: remove EXPORT_SYMBOL(kernel_thread)
222When: August 2006
223Files: arch/*/kernel/*_ksyms.c
Andy Whitcroftf0a594c2007-07-19 01:48:34 -0700224Check: kernel_thread
Christoph Hellwigac515892006-03-24 03:18:22 -0800225Why: kernel_thread is a low-level implementation detail. Drivers should
226 use the <linux/kthread.h> API instead which shields them from
227 implementation details and provides a higherlevel interface that
228 prevents bugs and code duplication
229Who: Christoph Hellwig <hch@lst.de>
230
231---------------------------
232
Arjan van de Venf71d20e2006-06-28 04:26:45 -0700233What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
234 (temporary transition config option provided until then)
235 The transition config option will also be removed at the same time.
236When: before 2.6.19
237Why: Unused symbols are both increasing the size of the kernel binary
238 and are often a sign of "wrong API"
239Who: Arjan van de Ven <arjan@linux.intel.com>
240
241---------------------------
242
Kay Sieversd81d9d62006-08-13 06:17:09 +0200243What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
Dominik Brodowskiacbd39f2006-09-30 22:41:43 -0400244When: October 2008
Kay Sieversd81d9d62006-08-13 06:17:09 +0200245Why: The stacking of class devices makes these values misleading and
246 inconsistent.
247 Class devices should not carry any of these properties, and bus
248 devices have SUBSYTEM and DRIVER as a replacement.
249Who: Kay Sievers <kay.sievers@suse.de>
250
251---------------------------
Jean Delvare6c805d22006-08-13 23:45:52 +0200252
Zhang Ruib981c592007-01-29 11:02:30 +0800253What: ACPI procfs interface
Zhang Rui8b8eb7d2007-07-18 17:23:24 +0800254When: July 2008
255Why: ACPI sysfs conversion should be finished by January 2008.
256 ACPI procfs interface will be removed in July 2008 so that
257 there is enough time for the user space to catch up.
Zhang Ruib981c592007-01-29 11:02:30 +0800258Who: Zhang Rui <rui.zhang@intel.com>
259
260---------------------------
261
Zhang Rui6d855fc2011-01-10 11:16:30 +0800262What: CONFIG_ACPI_PROCFS_POWER
263When: 2.6.39
264Why: sysfs I/F for ACPI power devices, including AC and Battery,
265 has been working in upstream kenrel since 2.6.24, Sep 2007.
266 In 2.6.37, we make the sysfs I/F always built in and this option
267 disabled by default.
268 Remove this option and the ACPI power procfs interface in 2.6.39.
269Who: Zhang Rui <rui.zhang@intel.com>
270
271---------------------------
272
Len Brown1bb67c22007-01-11 01:49:44 -0500273What: /proc/acpi/button
274When: August 2007
275Why: /proc/acpi/button has been replaced by events to the input layer
276 since 2.6.20.
277Who: Len Brown <len.brown@intel.com>
278
279---------------------------
Jeff Garzik54b290a2007-01-23 00:29:01 -0500280
Len Brown14e04fb2007-08-23 15:20:26 -0400281What: /proc/acpi/event
282When: February 2008
283Why: /proc/acpi/event has been replaced by events via the input layer
284 and netlink since 2.6.23.
285Who: Len Brown <len.brown@intel.com>
286
287---------------------------
288
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200289What: i386/x86_64 bzImage symlinks
Ingo Molnar19b4e7f2008-04-10 10:12:27 +0200290When: April 2010
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200291
292Why: The i386/x86_64 merge provides a symlink to the old bzImage
293 location so not yet updated user space tools, e.g. package
294 scripts, do not break.
295Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds038a5002007-10-11 19:40:14 -0700296
297---------------------------
298
David Brownell8a0cecf2009-04-02 16:57:06 -0700299What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib
300When: February 2010
301Why: All callers should use explicit gpio_request()/gpio_free().
302 The autorequest mechanism in gpiolib was provided mostly as a
303 migration aid for legacy GPIO interfaces (for SOC based GPIOs).
304 Those users have now largely migrated. Platforms implementing
305 the GPIO interfaces without using gpiolib will see no changes.
306Who: David Brownell <dbrownell@users.sourceforge.net>
307---------------------------
308
Michael Buescheb189d8b2008-01-28 14:47:41 -0800309What: b43 support for firmware revision < 410
Michael Bueschc5572892008-12-27 18:26:39 +0100310When: The schedule was July 2008, but it was decided that we are going to keep the
311 code as long as there are no major maintanance headaches.
312 So it _could_ be removed _any_ time now, if it conflicts with something new.
Michael Buescheb189d8b2008-01-28 14:47:41 -0800313Why: The support code for the old firmware hurts code readability/maintainability
314 and slightly hurts runtime performance. Bugfixes for the old firmware
315 are not provided by Broadcom anymore.
316Who: Michael Buesch <mb@bu3sch.de>
David S. Millere88bb412008-02-09 23:08:53 -0800317
318---------------------------
319
Mark Fasheh52f7c212008-01-29 17:08:26 -0800320What: /sys/o2cb symlink
321When: January 2010
322Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb
323 exists as a symlink for backwards compatibility for old versions of
324 ocfs2-tools. 2 years should be sufficient time to phase in new versions
325 which know to look in /sys/fs/o2cb.
326Who: ocfs2-devel@oss.oracle.com
Matthew Wilcoxd2f5e802008-04-19 13:49:34 -0400327
328---------------------------
329
Ravikiran G Thirumalai2584e512009-03-31 15:21:26 -0700330What: Ability for non root users to shm_get hugetlb pages based on mlock
331 resource limits
332When: 2.6.31
333Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or
334 have CAP_IPC_LOCK to be able to allocate shm segments backed by
335 huge pages. The mlock based rlimit check to allow shm hugetlb is
336 inconsistent with mmap based allocations. Hence it is being
337 deprecated.
338Who: Ravikiran Thirumalai <kiran@scalex86.org>
339
340---------------------------
341
Rene Herman16d75232008-06-24 19:38:56 +0200342What: CONFIG_THERMAL_HWMON
343When: January 2009
344Why: This option was introduced just to allow older lm-sensors userspace
345 to keep working over the upgrade to 2.6.26. At the scheduled time of
346 removal fixed lm-sensors (2.x or 3.x) should be readily available.
347Who: Rene Herman <rene.herman@gmail.com>
Johannes Berg22bb1be2008-07-10 11:16:47 +0200348
349---------------------------
350
351What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
352 (in net/core/net-sysfs.c)
353When: After the only user (hal) has seen a release with the patches
354 for enough time, probably some time in 2010.
355Why: Over 1K .text/.data size reduction, data is available in other
356 ways (ioctls)
357Who: Johannes Berg <johannes@sipsolutions.net>
Krzysztof Piotr Oledzki58401572008-07-21 10:01:34 -0700358
359---------------------------
360
Dave Jones753b7ae2009-03-09 15:14:37 -0400361What: sysfs ui for changing p4-clockmod parameters
362When: September 2009
363Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
364 e088e4c9cdb618675874becb91b2fd581ee707e6.
365 Removal is subject to fixing any remaining bugs in ACPI which may
366 cause the thermal throttling not to happen at the right time.
367Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
Thomas Gleixner0e57aa12009-03-13 14:34:05 +0100368
369-----------------------------
370
Alex Chiangf110ca42009-03-20 14:56:56 -0600371What: fakephp and associated sysfs files in /sys/bus/pci/slots/
372When: 2011
373Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
374 represent a machine's physical PCI slots. The change in semantics
375 had userspace implications, as the hotplug core no longer allowed
376 drivers to create multiple sysfs files per physical slot (required
377 for multi-function devices, e.g.). fakephp was seen as a developer's
378 tool only, and its interface changed. Too late, we learned that
379 there were some users of the fakephp interface.
380
381 In 2.6.30, the original fakephp interface was restored. At the same
382 time, the PCI core gained the ability that fakephp provided, namely
383 function-level hot-remove and hot-add.
384
385 Since the PCI core now provides the same functionality, exposed in:
386
387 /sys/bus/pci/rescan
388 /sys/bus/pci/devices/.../remove
389 /sys/bus/pci/devices/.../rescan
390
391 there is no functional reason to maintain fakephp as well.
392
393 We will keep the existing module so that 'modprobe fakephp' will
394 present the old /sys/bus/pci/slots/... interface for compatibility,
395 but users are urged to migrate their applications to the API above.
396
397 After a reasonable transition period, we will remove the legacy
398 fakephp interface.
399Who: Alex Chiang <achiang@hp.com>
Jean Delvare3f307fb2009-04-13 17:02:13 +0200400
401---------------------------
402
Johannes Bergc64fb012009-06-02 13:01:38 +0200403What: CONFIG_RFKILL_INPUT
404When: 2.6.33
405Why: Should be implemented in userspace, policy daemon.
406Who: Johannes Berg <johannes@sipsolutions.net>
David S. Miller9cbc1cb2009-06-15 03:02:23 -0700407
Andi Kleen45f458e2009-04-28 23:18:26 +0200408----------------------------
409
Tejun Heo93fe4482009-08-06 18:14:26 +0900410What: sound-slot/service-* module aliases and related clutters in
411 sound/sound_core.c
412When: August 2010
413Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
414 (14) and requests modules using custom sound-slot/service-*
415 module aliases. The only benefit of doing this is allowing
416 use of custom module aliases which might as well be considered
417 a bug at this point. This preemptive claiming prevents
418 alternative OSS implementations.
419
420 Till the feature is removed, the kernel will be requesting
421 both sound-slot/service-* and the standard char-major-* module
422 aliases and allow turning off the pre-claiming selectively via
423 CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss
424 kernel parameter.
425
426 After the transition phase is complete, both the custom module
427 aliases and switches to disable it will go away. This removal
428 will also allow making ALSA OSS emulation independent of
429 sound_core. The dependency will be broken then too.
430Who: Tejun Heo <tj@kernel.org>
Alok Katariad0153ca2009-09-29 10:25:24 -0700431
432----------------------------
433
Corentin Chary728900f2009-12-03 07:45:17 +0000434What: Support for lcd_switch and display_get in asus-laptop driver
435When: March 2010
436Why: These two features use non-standard interfaces. There are the
437 only features that really need multiple path to guess what's
438 the right method name on a specific laptop.
439
440 Removing them will allow to remove a lot of code an significantly
441 clean the drivers.
442
443 This will affect the backlight code which won't be able to know
444 if the backlight is on or off. The platform display file will also be
445 write only (like the one in eeepc-laptop).
446
447 This should'nt affect a lot of user because they usually know
448 when their display is on or off.
449
450Who: Corentin Chary <corentin.chary@gmail.com>
451
452----------------------------
Hans de Goedeceafe1d2010-01-11 10:50:53 -0200453
florian@mickler.org69c86372010-02-24 12:05:16 +0100454What: sysfs-class-rfkill state file
455When: Feb 2014
456Files: net/rfkill/core.c
457Why: Documented as obsolete since Feb 2010. This file is limited to 3
458 states while the rfkill drivers can have 4 states.
459Who: anybody or Florian Mickler <florian@mickler.org>
460
461----------------------------
462
463What: sysfs-class-rfkill claim file
464When: Feb 2012
465Files: net/rfkill/core.c
466Why: It is not possible to claim an rfkill driver since 2007. This is
467 Documented as obsolete since Feb 2010.
468Who: anybody or Florian Mickler <florian@mickler.org>
469
470----------------------------
471
Jan Kiszka79e95f42010-02-08 10:12:44 +0000472What: capifs
473When: February 2011
474Files: drivers/isdn/capi/capifs.*
475Why: udev fully replaces this special file system that only contains CAPI
476 NCCI TTY device nodes. User space (pppdcapiplugin) works without
477 noticing the difference.
478Who: Jan Kiszka <jan.kiszka@web.de>
Linus Torvaldsc812a512010-03-05 13:12:34 -0800479
480----------------------------
481
Avi Kivitydb358792010-01-26 16:30:06 +0200482What: KVM paravirt mmu host support
483When: January 2011
484Why: The paravirt mmu host support is slower than non-paravirt mmu, both
485 on newer and older hardware. It is already not exposed to the guest,
486 and kept only for live migration purposes.
487Who: Avi Kivity <avi@redhat.com>
Linus Torvaldsc812a512010-03-05 13:12:34 -0800488
489----------------------------
Len Brown4c81ba42010-03-14 16:28:46 -0400490
Wey-Yi Guy2b068612010-03-22 09:17:39 -0700491What: iwlwifi 50XX module parameters
492When: 2.6.40
493Why: The "..50" modules parameters were used to configure 5000 series and
494 up devices; different set of module parameters also available for 4965
495 with same functionalities. Consolidate both set into single place
496 in drivers/net/wireless/iwlwifi/iwl-agn.c
497
498Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Wey-Yi Guyd34a5a62010-03-23 10:17:03 -0700499
500----------------------------
501
502What: iwl4965 alias support
503When: 2.6.40
504Why: Internal alias support has been present in module-init-tools for some
505 time, the MODULE_ALIAS("iwl4965") boilerplate aliases can be removed
506 with no impact.
507
508Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Patrick McHardy62910552010-04-20 16:02:01 +0200509
Jan Engelhardt0cb47ea2010-03-16 18:25:12 +0100510---------------------------
511
512What: xt_NOTRACK
513Files: net/netfilter/xt_NOTRACK.c
514When: April 2011
515Why: Superseded by xt_CT
516Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
David S. Miller278554b2010-05-12 00:05:35 -0700517
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700518----------------------------
519
Thomas Gleixner6932bf32010-03-26 00:06:55 +0000520What: IRQF_DISABLED
521When: 2.6.36
522Why: The flag is a NOOP as we run interrupt handlers with interrupts disabled
523Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700524
525----------------------------
526
Rafael J. Wysocki72ad5d72010-07-23 22:59:09 +0200527What: The acpi_sleep=s4_nonvs command line option
528When: 2.6.37
529Files: arch/x86/kernel/acpi/sleep.c
530Why: superseded by acpi_sleep=nonvs
531Who: Rafael J. Wysocki <rjw@sisk.pl>
532
533----------------------------
FUJITA Tomonori17583362010-08-10 18:03:26 -0700534
535What: PCI DMA unmap state API
536When: August 2012
537Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced
538 with DMA unmap state API (DMA unmap state API can be used for
539 any bus).
540Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
541
542----------------------------
FUJITA Tomonoria35274c2010-08-10 18:03:26 -0700543
544What: DMA_xxBIT_MASK macros
545When: Jun 2011
546Why: DMA_xxBIT_MASK macros were replaced with DMA_BIT_MASK() macros.
547Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
548
549----------------------------
550
Daniel Lezcano45531752010-10-27 15:33:38 -0700551What: namespace cgroup (ns_cgroup)
552When: 2.6.38
553Why: The ns_cgroup leads to some problems:
554 * cgroup creation is out-of-control
555 * cgroup name can conflict when pids are looping
556 * it is not possible to have a single process handling
557 a lot of namespaces without falling in a exponential creation time
558 * we may want to create a namespace without creating a cgroup
559
560 The ns_cgroup is replaced by a compatibility flag 'clone_children',
561 where a newly created cgroup will copy the parent cgroup values.
562 The userspace has to manually create a cgroup and add a task to
563 the 'tasks' file.
564Who: Daniel Lezcano <daniel.lezcano@free.fr>
565
566----------------------------
567
Wey-Yi Guy72645ef2010-10-06 07:42:43 -0700568What: iwlwifi disable_hw_scan module parameters
569When: 2.6.40
570Why: Hareware scan is the prefer method for iwlwifi devices for
571 scanning operation. Remove software scan support for all the
572 iwlwifi devices.
573
574Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
575
576----------------------------
Linus Torvalds43901102010-10-26 09:55:25 -0700577
NeilBrownc67874f2010-09-22 12:55:07 +1000578What: access to nfsd auth cache through sys_nfsservctl or '.' files
579 in the 'nfsd' filesystem.
580When: 2.6.40
581Why: This is a legacy interface which have been replaced by a more
582 dynamic cache. Continuing to maintain this interface is an
583 unnecessary burden.
584Who: NeilBrown <neilb@suse.de>
585
586----------------------------
Jean Delvaree1e18ee2010-11-15 22:40:38 +0100587
588What: i2c_adapter.id
589When: June 2011
590Why: This field is deprecated. I2C device drivers shouldn't change their
591 behavior based on the underlying I2C adapter. Instead, the I2C
592 adapter driver should instantiate the I2C devices and provide the
593 needed platform-specific information.
594Who: Jean Delvare <khali@linux-fr.org>
595
596----------------------------
Tejun Heoed413902010-12-14 16:23:10 +0100597
598What: cancel_rearming_delayed_work[queue]()
599When: 2.6.39
600
601Why: The functions have been superceded by cancel_delayed_work_sync()
602 quite some time ago. The conversion is trivial and there is no
603 in-kernel user left.
604Who: Tejun Heo <tj@kernel.org>
605
606----------------------------
Jean Delvare632bdb22011-01-12 21:55:10 +0100607
608What: Legacy, non-standard chassis intrusion detection interface.
609When: June 2011
610Why: The adm9240, w83792d and w83793 hardware monitoring drivers have
611 legacy interfaces for chassis intrusion detection. A standard
612 interface has been added to each driver, so the legacy interface
613 can be removed.
614Who: Jean Delvare <khali@linux-fr.org>
615
616----------------------------
Patrick McHardy82d800d2011-01-20 10:33:55 +0100617
Jan Engelhardtcc4fc022011-01-18 17:32:40 +0100618What: xt_connlimit rev 0
619When: 2012
620Who: Jan Engelhardt <jengelh@medozas.de>
621Files: net/netfilter/xt_connlimit.c
622
623----------------------------
David S. Millerda935c62011-02-19 19:17:35 -0800624
Michal Hocko552b3722011-02-01 15:52:31 -0800625What: noswapaccount kernel command line parameter
626When: 2.6.40
627Why: The original implementation of memsw feature enabled by
628 CONFIG_CGROUP_MEM_RES_CTLR_SWAP could be disabled by the noswapaccount
629 kernel parameter (introduced in 2.6.29-rc1). Later on, this decision
630 turned out to be not ideal because we cannot have the feature compiled
631 in and disabled by default and let only interested to enable it
632 (e.g. general distribution kernels might need it). Therefore we have
633 added swapaccount[=0|1] parameter (introduced in 2.6.37) which provides
634 the both possibilities. If we remove noswapaccount we will have
635 less command line parameters with the same functionality and we
636 can also cleanup the parameter handling a bit ().
637Who: Michal Hocko <mhocko@suse.cz>
638
639----------------------------