blob: e4b57756b9f55a7786adab34da6bcb70ef31beaa [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
Len Brown99c63222011-04-01 15:19:23 -04009What: CONFIG_APM_CPU_IDLE, and its ability to call APM BIOS in idle
10When: 2012
11Why: This optional sub-feature of APM is of dubious reliability,
12 and ancient APM laptops are likely better served by calling HLT.
13 Deleting CONFIG_APM_CPU_IDLE allows x86 to stop exporting
14 the pm_idle function pointer to modules.
15Who: Len Brown <len.brown@intel.com>
16
17----------------------------
18
Len Browncdaab4a2011-04-01 15:41:17 -040019What: x86_32 "no-hlt" cmdline param
20When: 2012
21Why: remove a branch from idle path, simplify code used by everybody.
22 This option disabled the use of HLT in idle and machine_halt()
23 for hardware that was flakey 15-years ago. Today we have
24 "idle=poll" that removed HLT from idle, and so if such a machine
25 is still running the upstream kernel, "idle=poll" is likely sufficient.
26Who: Len Brown <len.brown@intel.com>
27
28----------------------------
29
Len Brown5d4c47e2011-04-01 15:46:09 -040030What: x86 "idle=mwait" cmdline param
31When: 2012
32Why: simplify x86 idle code
33Who: Len Brown <len.brown@intel.com>
34
35----------------------------
36
Luis R. Rodriguez4d8cd262009-09-08 12:09:47 -070037What: PRISM54
38When: 2.6.34
39
40Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the
41 prism54 wireless driver. After Intersil stopped selling these
42 devices in preference for the newer more flexible SoftMAC devices
43 a SoftMAC device driver was required and prism54 did not support
44 them. The p54pci driver now exists and has been present in the kernel for
45 a while. This driver supports both SoftMAC devices and FullMAC devices.
46 The main difference between these devices was the amount of memory which
47 could be used for the firmware. The SoftMAC devices support a smaller
48 amount of memory. Because of this the SoftMAC firmware fits into FullMAC
49 devices's memory. p54pci supports not only PCI / Cardbus but also USB
50 and SPI. Since p54pci supports all devices prism54 supports
51 you will have a conflict. I'm not quite sure how distributions are
52 handling this conflict right now. prism54 was kept around due to
53 claims users may experience issues when using the SoftMAC driver.
54 Time has passed users have not reported issues. If you use prism54
55 and for whatever reason you cannot use p54pci please let us know!
56 E-mail us at: linux-wireless@vger.kernel.org
57
58 For more information see the p54 wiki page:
59
60 http://wireless.kernel.org/en/users/Drivers/p54
61
62Who: Luis R. Rodriguez <lrodriguez@atheros.com>
63
64---------------------------
65
Robin Getz9d9b8fb2009-06-17 16:25:54 -070066What: IRQF_SAMPLE_RANDOM
67Check: IRQF_SAMPLE_RANDOM
68When: July 2009
69
70Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy
71 sources in the kernel's current entropy model. To resolve this, every
72 input point to the kernel's entropy pool needs to better document the
73 type of entropy source it actually is. This will be replaced with
74 additional add_*_randomness functions in drivers/char/random.c
75
76Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com>
77
78---------------------------
79
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -040080What: The ieee80211_regdom module parameter
Luis R. Rodriguez8a5117d2009-03-24 21:21:07 -040081When: March 2010 / desktop catchup
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -040082
83Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code,
84 and currently serves as an option for users to define an
85 ISO / IEC 3166 alpha2 code for the country they are currently
86 present in. Although there are userspace API replacements for this
87 through nl80211 distributions haven't yet caught up with implementing
88 decent alternatives through standard GUIs. Although available as an
89 option through iw or wpa_supplicant its just a matter of time before
90 distributions pick up good GUI options for this. The ideal solution
91 would actually consist of intelligent designs which would do this for
92 the user automatically even when travelling through different countries.
93 Until then we leave this module parameter as a compromise.
94
95 When userspace improves with reasonable widely-available alternatives for
96 this we will no longer need this module parameter. This entry hopes that
97 by the super-futuristically looking date of "March 2010" we will have
98 such replacements widely available.
99
100Who: Luis R. Rodriguez <lrodriguez@atheros.com>
101
102---------------------------
103
Alan Stern471d0552007-07-12 16:55:07 -0400104What: dev->power.power_state
Pavel Machek1ebfd792006-08-30 13:50:27 -0700105When: July 2007
106Why: Broken design for runtime control over driver power states, confusing
107 driver-internal runtime power management with: mechanisms to support
108 system-wide sleep state transitions; event codes that distinguish
109 different phases of swsusp "sleep" transitions; and userspace policy
110 inputs. This framework was never widely used, and most attempts to
111 use it were broken. Drivers should instead be exposing domain-specific
112 interfaces either to kernel or to userspace.
Pavel Macheka2531292010-07-18 14:27:13 +0200113Who: Pavel Machek <pavel@ucw.cz>
Pavel Machek1ebfd792006-08-30 13:50:27 -0700114
115---------------------------
116
David Rientjes51b1bd22010-08-09 17:19:47 -0700117What: /proc/<pid>/oom_adj
118When: August 2012
119Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's
120 badness heuristic used to determine which task to kill when the kernel
121 is out of memory.
122
123 The badness heuristic has since been rewritten since the introduction of
124 this tunable such that its meaning is deprecated. The value was
125 implemented as a bitshift on a score generated by the badness()
126 function that did not have any precise units of measure. With the
127 rewrite, the score is given as a proportion of available memory to the
128 task allocating pages, so using a bitshift which grows the score
129 exponentially is, thus, impossible to tune with fine granularity.
130
131 A much more powerful interface, /proc/<pid>/oom_score_adj, was
132 introduced with the oom killer rewrite that allows users to increase or
David Rientjes11239832011-07-25 17:12:17 -0700133 decrease the badness score linearly. This interface will replace
David Rientjes51b1bd22010-08-09 17:19:47 -0700134 /proc/<pid>/oom_adj.
135
136 A warning will be emitted to the kernel log if an application uses this
137 deprecated interface. After it is printed once, future warnings will be
138 suppressed until the kernel is rebooted.
139
140---------------------------
141
Christoph Hellwigac515892006-03-24 03:18:22 -0800142What: remove EXPORT_SYMBOL(kernel_thread)
143When: August 2006
144Files: arch/*/kernel/*_ksyms.c
Andy Whitcroftf0a594c2007-07-19 01:48:34 -0700145Check: kernel_thread
Christoph Hellwigac515892006-03-24 03:18:22 -0800146Why: kernel_thread is a low-level implementation detail. Drivers should
147 use the <linux/kthread.h> API instead which shields them from
148 implementation details and provides a higherlevel interface that
149 prevents bugs and code duplication
150Who: Christoph Hellwig <hch@lst.de>
151
152---------------------------
153
Arjan van de Venf71d20e2006-06-28 04:26:45 -0700154What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
155 (temporary transition config option provided until then)
156 The transition config option will also be removed at the same time.
157When: before 2.6.19
158Why: Unused symbols are both increasing the size of the kernel binary
159 and are often a sign of "wrong API"
160Who: Arjan van de Ven <arjan@linux.intel.com>
161
162---------------------------
163
Kay Sieversd81d9d62006-08-13 06:17:09 +0200164What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
Dominik Brodowskiacbd39f2006-09-30 22:41:43 -0400165When: October 2008
Kay Sieversd81d9d62006-08-13 06:17:09 +0200166Why: The stacking of class devices makes these values misleading and
167 inconsistent.
168 Class devices should not carry any of these properties, and bus
169 devices have SUBSYTEM and DRIVER as a replacement.
170Who: Kay Sievers <kay.sievers@suse.de>
171
172---------------------------
Jean Delvare6c805d22006-08-13 23:45:52 +0200173
Zhang Ruib981c592007-01-29 11:02:30 +0800174What: ACPI procfs interface
Zhang Rui8b8eb7d2007-07-18 17:23:24 +0800175When: July 2008
176Why: ACPI sysfs conversion should be finished by January 2008.
177 ACPI procfs interface will be removed in July 2008 so that
178 there is enough time for the user space to catch up.
Zhang Ruib981c592007-01-29 11:02:30 +0800179Who: Zhang Rui <rui.zhang@intel.com>
180
181---------------------------
182
Zhang Rui6d855fc2011-01-10 11:16:30 +0800183What: CONFIG_ACPI_PROCFS_POWER
184When: 2.6.39
185Why: sysfs I/F for ACPI power devices, including AC and Battery,
Justin P. Mattock70f23fd2011-05-10 10:16:21 +0200186 has been working in upstream kernel since 2.6.24, Sep 2007.
Zhang Rui6d855fc2011-01-10 11:16:30 +0800187 In 2.6.37, we make the sysfs I/F always built in and this option
188 disabled by default.
189 Remove this option and the ACPI power procfs interface in 2.6.39.
190Who: Zhang Rui <rui.zhang@intel.com>
191
192---------------------------
193
Len Brown14e04fb2007-08-23 15:20:26 -0400194What: /proc/acpi/event
195When: February 2008
196Why: /proc/acpi/event has been replaced by events via the input layer
197 and netlink since 2.6.23.
198Who: Len Brown <len.brown@intel.com>
199
200---------------------------
201
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200202What: i386/x86_64 bzImage symlinks
Ingo Molnar19b4e7f2008-04-10 10:12:27 +0200203When: April 2010
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200204
205Why: The i386/x86_64 merge provides a symlink to the old bzImage
206 location so not yet updated user space tools, e.g. package
207 scripts, do not break.
208Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds038a5002007-10-11 19:40:14 -0700209
210---------------------------
211
David Brownell8a0cecf2009-04-02 16:57:06 -0700212What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib
213When: February 2010
214Why: All callers should use explicit gpio_request()/gpio_free().
215 The autorequest mechanism in gpiolib was provided mostly as a
216 migration aid for legacy GPIO interfaces (for SOC based GPIOs).
217 Those users have now largely migrated. Platforms implementing
218 the GPIO interfaces without using gpiolib will see no changes.
219Who: David Brownell <dbrownell@users.sourceforge.net>
220---------------------------
221
Michael Buescheb189d82008-01-28 14:47:41 -0800222What: b43 support for firmware revision < 410
Michael Bueschc5572892008-12-27 18:26:39 +0100223When: The schedule was July 2008, but it was decided that we are going to keep the
224 code as long as there are no major maintanance headaches.
225 So it _could_ be removed _any_ time now, if it conflicts with something new.
Michael Buescheb189d82008-01-28 14:47:41 -0800226Why: The support code for the old firmware hurts code readability/maintainability
227 and slightly hurts runtime performance. Bugfixes for the old firmware
228 are not provided by Broadcom anymore.
Michael Büscheb032b92011-07-04 20:50:05 +0200229Who: Michael Buesch <m@bues.ch>
David S. Millere88bb412008-02-09 23:08:53 -0800230
231---------------------------
232
Ravikiran G Thirumalai2584e512009-03-31 15:21:26 -0700233What: Ability for non root users to shm_get hugetlb pages based on mlock
234 resource limits
235When: 2.6.31
236Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or
237 have CAP_IPC_LOCK to be able to allocate shm segments backed by
238 huge pages. The mlock based rlimit check to allow shm hugetlb is
239 inconsistent with mmap based allocations. Hence it is being
240 deprecated.
241Who: Ravikiran Thirumalai <kiran@scalex86.org>
242
243---------------------------
244
Johannes Berg22bb1be2008-07-10 11:16:47 +0200245What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
246 (in net/core/net-sysfs.c)
Johannes Berg0052d812011-12-06 20:45:37 +0100247When: 3.5
Johannes Berg22bb1be2008-07-10 11:16:47 +0200248Why: Over 1K .text/.data size reduction, data is available in other
249 ways (ioctls)
250Who: Johannes Berg <johannes@sipsolutions.net>
Krzysztof Piotr Oledzki58401572008-07-21 10:01:34 -0700251
252---------------------------
253
Dave Jones753b7ae2009-03-09 15:14:37 -0400254What: sysfs ui for changing p4-clockmod parameters
255When: September 2009
256Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
257 e088e4c9cdb618675874becb91b2fd581ee707e6.
258 Removal is subject to fixing any remaining bugs in ACPI which may
259 cause the thermal throttling not to happen at the right time.
260Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
Thomas Gleixner0e57aa12009-03-13 14:34:05 +0100261
262-----------------------------
263
Alex Chiangf110ca42009-03-20 14:56:56 -0600264What: fakephp and associated sysfs files in /sys/bus/pci/slots/
265When: 2011
266Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
267 represent a machine's physical PCI slots. The change in semantics
268 had userspace implications, as the hotplug core no longer allowed
269 drivers to create multiple sysfs files per physical slot (required
270 for multi-function devices, e.g.). fakephp was seen as a developer's
271 tool only, and its interface changed. Too late, we learned that
272 there were some users of the fakephp interface.
273
274 In 2.6.30, the original fakephp interface was restored. At the same
275 time, the PCI core gained the ability that fakephp provided, namely
276 function-level hot-remove and hot-add.
277
278 Since the PCI core now provides the same functionality, exposed in:
279
280 /sys/bus/pci/rescan
281 /sys/bus/pci/devices/.../remove
282 /sys/bus/pci/devices/.../rescan
283
284 there is no functional reason to maintain fakephp as well.
285
286 We will keep the existing module so that 'modprobe fakephp' will
287 present the old /sys/bus/pci/slots/... interface for compatibility,
288 but users are urged to migrate their applications to the API above.
289
290 After a reasonable transition period, we will remove the legacy
291 fakephp interface.
292Who: Alex Chiang <achiang@hp.com>
Jean Delvare3f307fb2009-04-13 17:02:13 +0200293
294---------------------------
295
Johannes Bergc64fb012009-06-02 13:01:38 +0200296What: CONFIG_RFKILL_INPUT
297When: 2.6.33
298Why: Should be implemented in userspace, policy daemon.
299Who: Johannes Berg <johannes@sipsolutions.net>
David S. Miller9cbc1cb2009-06-15 03:02:23 -0700300
Andi Kleen45f458e2009-04-28 23:18:26 +0200301----------------------------
302
Tejun Heo93fe4482009-08-06 18:14:26 +0900303What: sound-slot/service-* module aliases and related clutters in
304 sound/sound_core.c
305When: August 2010
306Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
307 (14) and requests modules using custom sound-slot/service-*
308 module aliases. The only benefit of doing this is allowing
309 use of custom module aliases which might as well be considered
310 a bug at this point. This preemptive claiming prevents
311 alternative OSS implementations.
312
313 Till the feature is removed, the kernel will be requesting
314 both sound-slot/service-* and the standard char-major-* module
315 aliases and allow turning off the pre-claiming selectively via
316 CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss
317 kernel parameter.
318
319 After the transition phase is complete, both the custom module
320 aliases and switches to disable it will go away. This removal
321 will also allow making ALSA OSS emulation independent of
322 sound_core. The dependency will be broken then too.
323Who: Tejun Heo <tj@kernel.org>
Alok Katariad0153ca2009-09-29 10:25:24 -0700324
325----------------------------
326
florian@mickler.org69c86372010-02-24 12:05:16 +0100327What: sysfs-class-rfkill state file
328When: Feb 2014
329Files: net/rfkill/core.c
330Why: Documented as obsolete since Feb 2010. This file is limited to 3
331 states while the rfkill drivers can have 4 states.
332Who: anybody or Florian Mickler <florian@mickler.org>
333
334----------------------------
335
336What: sysfs-class-rfkill claim file
337When: Feb 2012
338Files: net/rfkill/core.c
339Why: It is not possible to claim an rfkill driver since 2007. This is
340 Documented as obsolete since Feb 2010.
341Who: anybody or Florian Mickler <florian@mickler.org>
342
343----------------------------
344
Wey-Yi Guy2b068612010-03-22 09:17:39 -0700345What: iwlwifi 50XX module parameters
Deepak Saxenad5b55a82011-06-09 15:03:03 -0700346When: 3.0
Wey-Yi Guy2b068612010-03-22 09:17:39 -0700347Why: The "..50" modules parameters were used to configure 5000 series and
348 up devices; different set of module parameters also available for 4965
349 with same functionalities. Consolidate both set into single place
350 in drivers/net/wireless/iwlwifi/iwl-agn.c
351
352Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Wey-Yi Guyd34a5a62010-03-23 10:17:03 -0700353
354----------------------------
355
356What: iwl4965 alias support
Deepak Saxenad5b55a82011-06-09 15:03:03 -0700357When: 3.0
Wey-Yi Guyd34a5a62010-03-23 10:17:03 -0700358Why: Internal alias support has been present in module-init-tools for some
359 time, the MODULE_ALIAS("iwl4965") boilerplate aliases can be removed
360 with no impact.
361
362Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Patrick McHardy62910552010-04-20 16:02:01 +0200363
Jan Engelhardt0cb47ea2010-03-16 18:25:12 +0100364---------------------------
365
366What: xt_NOTRACK
367Files: net/netfilter/xt_NOTRACK.c
368When: April 2011
369Why: Superseded by xt_CT
370Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
David S. Miller278554b2010-05-12 00:05:35 -0700371
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700372----------------------------
373
Thomas Gleixner6932bf32010-03-26 00:06:55 +0000374What: IRQF_DISABLED
375When: 2.6.36
376Why: The flag is a NOOP as we run interrupt handlers with interrupts disabled
377Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700378
379----------------------------
380
FUJITA Tomonori17583362010-08-10 18:03:26 -0700381What: PCI DMA unmap state API
382When: August 2012
383Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced
384 with DMA unmap state API (DMA unmap state API can be used for
385 any bus).
386Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
387
388----------------------------
FUJITA Tomonoria35274c2010-08-10 18:03:26 -0700389
Wey-Yi Guy72645ef2010-10-06 07:42:43 -0700390What: iwlwifi disable_hw_scan module parameters
Deepak Saxenad5b55a82011-06-09 15:03:03 -0700391When: 3.0
Wey-Yi Guy72645ef2010-10-06 07:42:43 -0700392Why: Hareware scan is the prefer method for iwlwifi devices for
393 scanning operation. Remove software scan support for all the
394 iwlwifi devices.
395
396Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
397
398----------------------------
Linus Torvalds43901102010-10-26 09:55:25 -0700399
Jean Delvare632bdb22011-01-12 21:55:10 +0100400What: Legacy, non-standard chassis intrusion detection interface.
401When: June 2011
402Why: The adm9240, w83792d and w83793 hardware monitoring drivers have
403 legacy interfaces for chassis intrusion detection. A standard
404 interface has been added to each driver, so the legacy interface
405 can be removed.
406Who: Jean Delvare <khali@linux-fr.org>
407
408----------------------------
Michal Hocko552b3722011-02-01 15:52:31 -0800409
Jan Engelhardtcc4fc022011-01-18 17:32:40 +0100410What: xt_connlimit rev 0
411When: 2012
412Who: Jan Engelhardt <jengelh@medozas.de>
413Files: net/netfilter/xt_connlimit.c
414
415----------------------------
David S. Millerda935c62011-02-19 19:17:35 -0800416
Florian Westphalde81bbe2011-03-15 20:16:20 +0100417What: ipt_addrtype match include file
418When: 2012
419Why: superseded by xt_addrtype
420Who: Florian Westphal <fw@strlen.de>
421Files: include/linux/netfilter_ipv4/ipt_addrtype.h
422
423----------------------------
Jean Delvarefe6fc252011-03-20 14:50:53 +0100424
425What: i2c_driver.attach_adapter
426 i2c_driver.detach_adapter
427When: September 2011
428Why: These legacy callbacks should no longer be used as i2c-core offers
429 a variety of preferable alternative ways to instantiate I2C devices.
430Who: Jean Delvare <khali@linux-fr.org>
431
432----------------------------
Laurent Pinchart1dc8ddf2010-10-12 12:11:30 -0300433
Hans Verkuil62936982011-06-13 09:38:54 -0300434What: Opening a radio device node will no longer automatically switch the
435 tuner mode from tv to radio.
436When: 3.3
437Why: Just opening a V4L device should not change the state of the hardware
438 like that. It's very unexpected and against the V4L spec. Instead, you
439 switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second
440 and last step of the move to consistent handling of tv and radio tuners.
441Who: Hans Verkuil <hans.verkuil@cisco.com>
442
443----------------------------
Linus Torvaldsf5499532011-07-25 23:08:32 -0700444
Alan Stern664a51a2011-06-15 16:31:37 -0400445What: g_file_storage driver
446When: 3.8
447Why: This driver has been superseded by g_mass_storage.
448Who: Alan Stern <stern@rowland.harvard.edu>
449
450----------------------------
Lee, Chun-Yi7b8aca62011-05-31 14:52:22 +0800451
452What: threeg and interface sysfs files in /sys/devices/platform/acer-wmi
453When: 2012
454Why: In 3.0, we can now autodetect internal 3G device and already have
455 the threeg rfkill device. So, we plan to remove threeg sysfs support
456 for it's no longer necessary.
457
458 We also plan to remove interface sysfs file that exposed which ACPI-WMI
459 interface that was used by acer-wmi driver. It will replaced by
460 information log when acer-wmi initial.
461Who: Lee, Chun-Yi <jlee@novell.com>
Christoph Hellwig242d6212011-08-24 05:57:51 +0000462
Michal Nazarewiczd327ab52011-11-19 18:27:37 +0100463---------------------------
464
465What: /sys/devices/platform/_UDC_/udc/_UDC_/is_dualspeed file and
466 is_dualspeed line in /sys/devices/platform/ci13xxx_*/udc/device file.
467When: 3.8
468Why: The is_dualspeed file is superseded by maximum_speed in the same
469 directory and is_dualspeed line in device file is superseded by
470 max_speed line in the same file.
471
472 The maximum_speed/max_speed specifies maximum speed supported by UDC.
473 To check if dualspeeed is supported, check if the value is >= 3.
474 Various possible speeds are defined in <linux/usb/ch9.h>.
475Who: Michal Nazarewicz <mina86@mina86.com>
476
Christoph Hellwig242d6212011-08-24 05:57:51 +0000477----------------------------
John W. Linville094daf72011-10-11 15:35:42 -0400478
Christoph Hellwig242d6212011-08-24 05:57:51 +0000479What: The XFS nodelaylog mount option
480When: 3.3
481Why: The delaylog mode that has been the default since 2.6.39 has proven
482 stable, and the old code is in the way of additional improvements in
483 the log code.
484Who: Christoph Hellwig <hch@lst.de>
John W. Linville094daf72011-10-11 15:35:42 -0400485
486----------------------------
487
Don Fry3c607d22011-09-30 11:40:20 -0700488What: iwlagn alias support
489When: 3.5
490Why: The iwlagn module has been renamed iwlwifi. The alias will be around
491 for backward compatibility for several cycles and then dropped.
John W. Linville094daf72011-10-11 15:35:42 -0400492Who: Don Fry <donald.h.fry@intel.com>
Bjorn Helgaas7e00fe22011-10-28 16:26:05 -0600493
494----------------------------
495
496What: pci_scan_bus_parented()
497When: 3.5
498Why: The pci_scan_bus_parented() interface creates a new root bus. The
499 bus is created with default resources (ioport_resource and
500 iomem_resource) that are always wrong, so we rely on arch code to
501 correct them later. Callers of pci_scan_bus_parented() should
502 convert to using pci_scan_root_bus() so they can supply a list of
503 bus resources when the bus is created.
504Who: Bjorn Helgaas <bhelgaas@google.com>
Nicolas Ferre08a52e12012-01-06 16:09:37 +0100505
506----------------------------
507
Sebastian Andrzej Siewior7396bd92012-03-15 21:59:36 +0100508What: Low Performance USB Block driver ("CONFIG_BLK_DEV_UB")
509When: 3.6
510Why: This driver provides support for USB storage devices like "USB
511 sticks". As of now, it is deactivated in Debian, Fedora and
512 Ubuntu. All current users can switch over to usb-storage
513 (CONFIG_USB_STORAGE) which only drawback is the additional SCSI
514 stack.
515Who: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Linus Torvalds9f393832012-03-21 09:40:26 -0700516
517----------------------------
518
Cong Wang317b6e12011-11-26 11:12:30 +0800519What: kmap_atomic(page, km_type)
520When: 3.5
521Why: The old kmap_atomic() with two arguments is deprecated, we only
522 keep it for backward compatibility for few cycles and then drop it.
523Who: Cong Wang <amwang@redhat.com>
Kees Cookec0c4272012-03-23 12:08:55 -0700524
525----------------------------
526
527What: get_robust_list syscall
528When: 2013
529Why: There appear to be no production users of the get_robust_list syscall,
530 and it runs the risk of leaking address locations, allowing the bypass
531 of ASLR. It was only ever intended for debugging, so it should be
532 removed.
533Who: Kees Cook <keescook@chromium.org>
Linus Torvaldsccb1ec92012-04-12 15:16:26 -0700534
535----------------------------
536
Sasikantha babuaa2bf9b2012-03-21 20:10:54 +0530537What: setitimer accepts user NULL pointer (value)
538When: 3.6
539Why: setitimer is not returning -EFAULT if user pointer is NULL. This
540 violates the spec.
541Who: Sasikantha Babu <sasikanth.v19@gmail.com>
Sylwester Nawrocki5694e022012-04-21 14:11:06 -0300542
543----------------------------
544
545What: V4L2_CID_HCENTER, V4L2_CID_VCENTER V4L2 controls
546When: 3.7
547Why: The V4L2_CID_VCENTER, V4L2_CID_HCENTER controls have been deprecated
548 for about 4 years and they are not used by any mainline driver.
549 There are newer controls (V4L2_CID_PAN*, V4L2_CID_TILT*) that provide
550 similar functionality.
551Who: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>