Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | The following is a list of files and features that are going to be |
| 2 | removed in the kernel source tree. Every entry should contain what |
| 3 | exactly is going away, why it is happening, and who is going to be doing |
| 4 | the work. When the feature is removed from the kernel, it should also |
Jim Cromie | f0b919d | 2012-04-27 14:30:36 -0600 | [diff] [blame] | 5 | be removed from this file. The suggested deprecation period is 3 releases. |
| 6 | |
| 7 | --------------------------- |
| 8 | |
| 9 | What: ddebug_query="query" boot cmdline param |
| 10 | When: v3.8 |
| 11 | Why: obsoleted by dyndbg="query" and module.dyndbg="query" |
| 12 | Who: Jim Cromie <jim.cromie@gmail.com>, Jason Baron <jbaron@redhat.com> |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 13 | |
| 14 | --------------------------- |
| 15 | |
Wanpeng Li | 3965c9a | 2012-07-31 16:41:52 -0700 | [diff] [blame] | 16 | What: /proc/sys/vm/nr_pdflush_threads |
| 17 | When: 2012 |
| 18 | Why: Since pdflush is deprecated, the interface exported in /proc/sys/vm/ |
| 19 | should be removed. |
| 20 | Who: Wanpeng Li <liwp@linux.vnet.ibm.com> |
| 21 | |
| 22 | --------------------------- |
| 23 | |
Len Brown | 99c6322 | 2011-04-01 15:19:23 -0400 | [diff] [blame] | 24 | What: CONFIG_APM_CPU_IDLE, and its ability to call APM BIOS in idle |
| 25 | When: 2012 |
| 26 | Why: This optional sub-feature of APM is of dubious reliability, |
| 27 | and ancient APM laptops are likely better served by calling HLT. |
| 28 | Deleting CONFIG_APM_CPU_IDLE allows x86 to stop exporting |
| 29 | the pm_idle function pointer to modules. |
| 30 | Who: Len Brown <len.brown@intel.com> |
| 31 | |
| 32 | ---------------------------- |
| 33 | |
Len Brown | cdaab4a | 2011-04-01 15:41:17 -0400 | [diff] [blame] | 34 | What: x86_32 "no-hlt" cmdline param |
| 35 | When: 2012 |
| 36 | Why: remove a branch from idle path, simplify code used by everybody. |
| 37 | This option disabled the use of HLT in idle and machine_halt() |
| 38 | for hardware that was flakey 15-years ago. Today we have |
| 39 | "idle=poll" that removed HLT from idle, and so if such a machine |
| 40 | is still running the upstream kernel, "idle=poll" is likely sufficient. |
| 41 | Who: Len Brown <len.brown@intel.com> |
| 42 | |
| 43 | ---------------------------- |
| 44 | |
Len Brown | 5d4c47e | 2011-04-01 15:46:09 -0400 | [diff] [blame] | 45 | What: x86 "idle=mwait" cmdline param |
| 46 | When: 2012 |
| 47 | Why: simplify x86 idle code |
| 48 | Who: Len Brown <len.brown@intel.com> |
| 49 | |
| 50 | ---------------------------- |
| 51 | |
Luis R. Rodriguez | 4d8cd26 | 2009-09-08 12:09:47 -0700 | [diff] [blame] | 52 | What: PRISM54 |
| 53 | When: 2.6.34 |
| 54 | |
| 55 | Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the |
| 56 | prism54 wireless driver. After Intersil stopped selling these |
| 57 | devices in preference for the newer more flexible SoftMAC devices |
| 58 | a SoftMAC device driver was required and prism54 did not support |
| 59 | them. The p54pci driver now exists and has been present in the kernel for |
| 60 | a while. This driver supports both SoftMAC devices and FullMAC devices. |
| 61 | The main difference between these devices was the amount of memory which |
| 62 | could be used for the firmware. The SoftMAC devices support a smaller |
| 63 | amount of memory. Because of this the SoftMAC firmware fits into FullMAC |
| 64 | devices's memory. p54pci supports not only PCI / Cardbus but also USB |
| 65 | and SPI. Since p54pci supports all devices prism54 supports |
| 66 | you will have a conflict. I'm not quite sure how distributions are |
| 67 | handling this conflict right now. prism54 was kept around due to |
| 68 | claims users may experience issues when using the SoftMAC driver. |
| 69 | Time has passed users have not reported issues. If you use prism54 |
| 70 | and for whatever reason you cannot use p54pci please let us know! |
| 71 | E-mail us at: linux-wireless@vger.kernel.org |
| 72 | |
| 73 | For more information see the p54 wiki page: |
| 74 | |
| 75 | http://wireless.kernel.org/en/users/Drivers/p54 |
| 76 | |
| 77 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 78 | |
| 79 | --------------------------- |
| 80 | |
Luis R. Rodriguez | 6ee7d33 | 2009-03-20 23:53:06 -0400 | [diff] [blame] | 81 | What: The ieee80211_regdom module parameter |
Luis R. Rodriguez | 8a5117d | 2009-03-24 21:21:07 -0400 | [diff] [blame] | 82 | When: March 2010 / desktop catchup |
Luis R. Rodriguez | 6ee7d33 | 2009-03-20 23:53:06 -0400 | [diff] [blame] | 83 | |
| 84 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, |
| 85 | and currently serves as an option for users to define an |
| 86 | ISO / IEC 3166 alpha2 code for the country they are currently |
| 87 | present in. Although there are userspace API replacements for this |
| 88 | through nl80211 distributions haven't yet caught up with implementing |
| 89 | decent alternatives through standard GUIs. Although available as an |
| 90 | option through iw or wpa_supplicant its just a matter of time before |
| 91 | distributions pick up good GUI options for this. The ideal solution |
| 92 | would actually consist of intelligent designs which would do this for |
| 93 | the user automatically even when travelling through different countries. |
| 94 | Until then we leave this module parameter as a compromise. |
| 95 | |
| 96 | When userspace improves with reasonable widely-available alternatives for |
| 97 | this we will no longer need this module parameter. This entry hopes that |
| 98 | by the super-futuristically looking date of "March 2010" we will have |
| 99 | such replacements widely available. |
| 100 | |
| 101 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
| 102 | |
| 103 | --------------------------- |
| 104 | |
Alan Stern | 471d055 | 2007-07-12 16:55:07 -0400 | [diff] [blame] | 105 | What: dev->power.power_state |
Pavel Machek | 1ebfd79 | 2006-08-30 13:50:27 -0700 | [diff] [blame] | 106 | When: July 2007 |
| 107 | Why: Broken design for runtime control over driver power states, confusing |
| 108 | driver-internal runtime power management with: mechanisms to support |
| 109 | system-wide sleep state transitions; event codes that distinguish |
| 110 | different phases of swsusp "sleep" transitions; and userspace policy |
| 111 | inputs. This framework was never widely used, and most attempts to |
| 112 | use it were broken. Drivers should instead be exposing domain-specific |
| 113 | interfaces either to kernel or to userspace. |
Pavel Machek | a253129 | 2010-07-18 14:27:13 +0200 | [diff] [blame] | 114 | Who: Pavel Machek <pavel@ucw.cz> |
Pavel Machek | 1ebfd79 | 2006-08-30 13:50:27 -0700 | [diff] [blame] | 115 | |
| 116 | --------------------------- |
| 117 | |
David Rientjes | 51b1bd2 | 2010-08-09 17:19:47 -0700 | [diff] [blame] | 118 | What: /proc/<pid>/oom_adj |
| 119 | When: August 2012 |
| 120 | Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's |
| 121 | badness heuristic used to determine which task to kill when the kernel |
| 122 | is out of memory. |
| 123 | |
| 124 | The badness heuristic has since been rewritten since the introduction of |
| 125 | this tunable such that its meaning is deprecated. The value was |
| 126 | implemented as a bitshift on a score generated by the badness() |
| 127 | function that did not have any precise units of measure. With the |
| 128 | rewrite, the score is given as a proportion of available memory to the |
| 129 | task allocating pages, so using a bitshift which grows the score |
| 130 | exponentially is, thus, impossible to tune with fine granularity. |
| 131 | |
| 132 | A much more powerful interface, /proc/<pid>/oom_score_adj, was |
| 133 | introduced with the oom killer rewrite that allows users to increase or |
David Rientjes | 1123983 | 2011-07-25 17:12:17 -0700 | [diff] [blame] | 134 | decrease the badness score linearly. This interface will replace |
David Rientjes | 51b1bd2 | 2010-08-09 17:19:47 -0700 | [diff] [blame] | 135 | /proc/<pid>/oom_adj. |
| 136 | |
| 137 | A warning will be emitted to the kernel log if an application uses this |
| 138 | deprecated interface. After it is printed once, future warnings will be |
| 139 | suppressed until the kernel is rebooted. |
| 140 | |
| 141 | --------------------------- |
| 142 | |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 143 | What: remove EXPORT_SYMBOL(kernel_thread) |
| 144 | When: August 2006 |
| 145 | Files: arch/*/kernel/*_ksyms.c |
Andy Whitcroft | f0a594c | 2007-07-19 01:48:34 -0700 | [diff] [blame] | 146 | Check: kernel_thread |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 147 | Why: kernel_thread is a low-level implementation detail. Drivers should |
| 148 | use the <linux/kthread.h> API instead which shields them from |
| 149 | implementation details and provides a higherlevel interface that |
| 150 | prevents bugs and code duplication |
| 151 | Who: Christoph Hellwig <hch@lst.de> |
| 152 | |
| 153 | --------------------------- |
| 154 | |
Arjan van de Ven | f71d20e | 2006-06-28 04:26:45 -0700 | [diff] [blame] | 155 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
| 156 | (temporary transition config option provided until then) |
| 157 | The transition config option will also be removed at the same time. |
| 158 | When: before 2.6.19 |
| 159 | Why: Unused symbols are both increasing the size of the kernel binary |
| 160 | and are often a sign of "wrong API" |
| 161 | Who: Arjan van de Ven <arjan@linux.intel.com> |
| 162 | |
| 163 | --------------------------- |
| 164 | |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 165 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment |
Dominik Brodowski | acbd39f | 2006-09-30 22:41:43 -0400 | [diff] [blame] | 166 | When: October 2008 |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 167 | Why: The stacking of class devices makes these values misleading and |
| 168 | inconsistent. |
| 169 | Class devices should not carry any of these properties, and bus |
| 170 | devices have SUBSYTEM and DRIVER as a replacement. |
| 171 | Who: Kay Sievers <kay.sievers@suse.de> |
| 172 | |
| 173 | --------------------------- |
Jean Delvare | 6c805d2 | 2006-08-13 23:45:52 +0200 | [diff] [blame] | 174 | |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 175 | What: ACPI procfs interface |
Zhang Rui | 8b8eb7d | 2007-07-18 17:23:24 +0800 | [diff] [blame] | 176 | When: July 2008 |
| 177 | Why: ACPI sysfs conversion should be finished by January 2008. |
| 178 | ACPI procfs interface will be removed in July 2008 so that |
| 179 | there is enough time for the user space to catch up. |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 180 | Who: Zhang Rui <rui.zhang@intel.com> |
| 181 | |
| 182 | --------------------------- |
| 183 | |
Zhang Rui | 6d855fc | 2011-01-10 11:16:30 +0800 | [diff] [blame] | 184 | What: CONFIG_ACPI_PROCFS_POWER |
| 185 | When: 2.6.39 |
| 186 | Why: sysfs I/F for ACPI power devices, including AC and Battery, |
Justin P. Mattock | 70f23fd | 2011-05-10 10:16:21 +0200 | [diff] [blame] | 187 | has been working in upstream kernel since 2.6.24, Sep 2007. |
Zhang Rui | 6d855fc | 2011-01-10 11:16:30 +0800 | [diff] [blame] | 188 | In 2.6.37, we make the sysfs I/F always built in and this option |
| 189 | disabled by default. |
| 190 | Remove this option and the ACPI power procfs interface in 2.6.39. |
| 191 | Who: Zhang Rui <rui.zhang@intel.com> |
| 192 | |
| 193 | --------------------------- |
| 194 | |
Len Brown | 14e04fb | 2007-08-23 15:20:26 -0400 | [diff] [blame] | 195 | What: /proc/acpi/event |
| 196 | When: February 2008 |
| 197 | Why: /proc/acpi/event has been replaced by events via the input layer |
| 198 | and netlink since 2.6.23. |
| 199 | Who: Len Brown <len.brown@intel.com> |
| 200 | |
| 201 | --------------------------- |
| 202 | |
Thomas Gleixner | 914d97f | 2007-10-11 11:20:05 +0200 | [diff] [blame] | 203 | What: i386/x86_64 bzImage symlinks |
Ingo Molnar | 19b4e7f | 2008-04-10 10:12:27 +0200 | [diff] [blame] | 204 | When: April 2010 |
Thomas Gleixner | 914d97f | 2007-10-11 11:20:05 +0200 | [diff] [blame] | 205 | |
| 206 | Why: The i386/x86_64 merge provides a symlink to the old bzImage |
| 207 | location so not yet updated user space tools, e.g. package |
| 208 | scripts, do not break. |
| 209 | Who: Thomas Gleixner <tglx@linutronix.de> |
Linus Torvalds | 038a500 | 2007-10-11 19:40:14 -0700 | [diff] [blame] | 210 | |
| 211 | --------------------------- |
| 212 | |
David Brownell | 8a0cecf | 2009-04-02 16:57:06 -0700 | [diff] [blame] | 213 | What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib |
| 214 | When: February 2010 |
| 215 | Why: All callers should use explicit gpio_request()/gpio_free(). |
| 216 | The autorequest mechanism in gpiolib was provided mostly as a |
| 217 | migration aid for legacy GPIO interfaces (for SOC based GPIOs). |
| 218 | Those users have now largely migrated. Platforms implementing |
| 219 | the GPIO interfaces without using gpiolib will see no changes. |
| 220 | Who: David Brownell <dbrownell@users.sourceforge.net> |
| 221 | --------------------------- |
| 222 | |
Michael Buesch | eb189d8b | 2008-01-28 14:47:41 -0800 | [diff] [blame] | 223 | What: b43 support for firmware revision < 410 |
Michael Buesch | c557289 | 2008-12-27 18:26:39 +0100 | [diff] [blame] | 224 | When: The schedule was July 2008, but it was decided that we are going to keep the |
| 225 | code as long as there are no major maintanance headaches. |
| 226 | So it _could_ be removed _any_ time now, if it conflicts with something new. |
Michael Buesch | eb189d8b | 2008-01-28 14:47:41 -0800 | [diff] [blame] | 227 | Why: The support code for the old firmware hurts code readability/maintainability |
| 228 | and slightly hurts runtime performance. Bugfixes for the old firmware |
| 229 | are not provided by Broadcom anymore. |
Michael Büsch | eb032b9 | 2011-07-04 20:50:05 +0200 | [diff] [blame] | 230 | Who: Michael Buesch <m@bues.ch> |
David S. Miller | e88bb41 | 2008-02-09 23:08:53 -0800 | [diff] [blame] | 231 | |
| 232 | --------------------------- |
| 233 | |
Ravikiran G Thirumalai | 2584e51 | 2009-03-31 15:21:26 -0700 | [diff] [blame] | 234 | What: Ability for non root users to shm_get hugetlb pages based on mlock |
| 235 | resource limits |
| 236 | When: 2.6.31 |
| 237 | Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or |
| 238 | have CAP_IPC_LOCK to be able to allocate shm segments backed by |
| 239 | huge pages. The mlock based rlimit check to allow shm hugetlb is |
| 240 | inconsistent with mmap based allocations. Hence it is being |
| 241 | deprecated. |
| 242 | Who: Ravikiran Thirumalai <kiran@scalex86.org> |
| 243 | |
| 244 | --------------------------- |
| 245 | |
Dave Jones | 753b7ae | 2009-03-09 15:14:37 -0400 | [diff] [blame] | 246 | What: sysfs ui for changing p4-clockmod parameters |
| 247 | When: September 2009 |
| 248 | Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and |
| 249 | e088e4c9cdb618675874becb91b2fd581ee707e6. |
| 250 | Removal is subject to fixing any remaining bugs in ACPI which may |
| 251 | cause the thermal throttling not to happen at the right time. |
| 252 | Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com> |
Thomas Gleixner | 0e57aa1 | 2009-03-13 14:34:05 +0100 | [diff] [blame] | 253 | |
| 254 | ----------------------------- |
| 255 | |
Alex Chiang | f110ca4 | 2009-03-20 14:56:56 -0600 | [diff] [blame] | 256 | What: fakephp and associated sysfs files in /sys/bus/pci/slots/ |
| 257 | When: 2011 |
| 258 | Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to |
| 259 | represent a machine's physical PCI slots. The change in semantics |
| 260 | had userspace implications, as the hotplug core no longer allowed |
| 261 | drivers to create multiple sysfs files per physical slot (required |
| 262 | for multi-function devices, e.g.). fakephp was seen as a developer's |
| 263 | tool only, and its interface changed. Too late, we learned that |
| 264 | there were some users of the fakephp interface. |
| 265 | |
| 266 | In 2.6.30, the original fakephp interface was restored. At the same |
| 267 | time, the PCI core gained the ability that fakephp provided, namely |
| 268 | function-level hot-remove and hot-add. |
| 269 | |
| 270 | Since the PCI core now provides the same functionality, exposed in: |
| 271 | |
| 272 | /sys/bus/pci/rescan |
| 273 | /sys/bus/pci/devices/.../remove |
| 274 | /sys/bus/pci/devices/.../rescan |
| 275 | |
| 276 | there is no functional reason to maintain fakephp as well. |
| 277 | |
| 278 | We will keep the existing module so that 'modprobe fakephp' will |
| 279 | present the old /sys/bus/pci/slots/... interface for compatibility, |
| 280 | but users are urged to migrate their applications to the API above. |
| 281 | |
| 282 | After a reasonable transition period, we will remove the legacy |
| 283 | fakephp interface. |
| 284 | Who: Alex Chiang <achiang@hp.com> |
Jean Delvare | 3f307fb | 2009-04-13 17:02:13 +0200 | [diff] [blame] | 285 | |
| 286 | --------------------------- |
| 287 | |
Johannes Berg | c64fb01 | 2009-06-02 13:01:38 +0200 | [diff] [blame] | 288 | What: CONFIG_RFKILL_INPUT |
| 289 | When: 2.6.33 |
| 290 | Why: Should be implemented in userspace, policy daemon. |
| 291 | Who: Johannes Berg <johannes@sipsolutions.net> |
David S. Miller | 9cbc1cb | 2009-06-15 03:02:23 -0700 | [diff] [blame] | 292 | |
Andi Kleen | 45f458e | 2009-04-28 23:18:26 +0200 | [diff] [blame] | 293 | ---------------------------- |
| 294 | |
Tejun Heo | 93fe448 | 2009-08-06 18:14:26 +0900 | [diff] [blame] | 295 | What: sound-slot/service-* module aliases and related clutters in |
| 296 | sound/sound_core.c |
| 297 | When: August 2010 |
| 298 | Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR |
| 299 | (14) and requests modules using custom sound-slot/service-* |
| 300 | module aliases. The only benefit of doing this is allowing |
| 301 | use of custom module aliases which might as well be considered |
| 302 | a bug at this point. This preemptive claiming prevents |
| 303 | alternative OSS implementations. |
| 304 | |
| 305 | Till the feature is removed, the kernel will be requesting |
| 306 | both sound-slot/service-* and the standard char-major-* module |
| 307 | aliases and allow turning off the pre-claiming selectively via |
| 308 | CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss |
| 309 | kernel parameter. |
| 310 | |
| 311 | After the transition phase is complete, both the custom module |
| 312 | aliases and switches to disable it will go away. This removal |
| 313 | will also allow making ALSA OSS emulation independent of |
| 314 | sound_core. The dependency will be broken then too. |
| 315 | Who: Tejun Heo <tj@kernel.org> |
Alok Kataria | d0153ca | 2009-09-29 10:25:24 -0700 | [diff] [blame] | 316 | |
| 317 | ---------------------------- |
| 318 | |
florian@mickler.org | 69c8637 | 2010-02-24 12:05:16 +0100 | [diff] [blame] | 319 | What: sysfs-class-rfkill state file |
| 320 | When: Feb 2014 |
| 321 | Files: net/rfkill/core.c |
| 322 | Why: Documented as obsolete since Feb 2010. This file is limited to 3 |
| 323 | states while the rfkill drivers can have 4 states. |
| 324 | Who: anybody or Florian Mickler <florian@mickler.org> |
| 325 | |
| 326 | ---------------------------- |
| 327 | |
| 328 | What: sysfs-class-rfkill claim file |
| 329 | When: Feb 2012 |
| 330 | Files: net/rfkill/core.c |
| 331 | Why: It is not possible to claim an rfkill driver since 2007. This is |
| 332 | Documented as obsolete since Feb 2010. |
| 333 | Who: anybody or Florian Mickler <florian@mickler.org> |
| 334 | |
| 335 | ---------------------------- |
| 336 | |
Wey-Yi Guy | 2b06861 | 2010-03-22 09:17:39 -0700 | [diff] [blame] | 337 | What: iwlwifi 50XX module parameters |
Deepak Saxena | d5b55a8 | 2011-06-09 15:03:03 -0700 | [diff] [blame] | 338 | When: 3.0 |
Wey-Yi Guy | 2b06861 | 2010-03-22 09:17:39 -0700 | [diff] [blame] | 339 | Why: The "..50" modules parameters were used to configure 5000 series and |
| 340 | up devices; different set of module parameters also available for 4965 |
| 341 | with same functionalities. Consolidate both set into single place |
| 342 | in drivers/net/wireless/iwlwifi/iwl-agn.c |
| 343 | |
| 344 | Who: Wey-Yi Guy <wey-yi.w.guy@intel.com> |
Wey-Yi Guy | d34a5a6 | 2010-03-23 10:17:03 -0700 | [diff] [blame] | 345 | |
| 346 | ---------------------------- |
| 347 | |
| 348 | What: iwl4965 alias support |
Deepak Saxena | d5b55a8 | 2011-06-09 15:03:03 -0700 | [diff] [blame] | 349 | When: 3.0 |
Wey-Yi Guy | d34a5a6 | 2010-03-23 10:17:03 -0700 | [diff] [blame] | 350 | Why: Internal alias support has been present in module-init-tools for some |
| 351 | time, the MODULE_ALIAS("iwl4965") boilerplate aliases can be removed |
| 352 | with no impact. |
| 353 | |
| 354 | Who: Wey-Yi Guy <wey-yi.w.guy@intel.com> |
Patrick McHardy | 6291055 | 2010-04-20 16:02:01 +0200 | [diff] [blame] | 355 | |
Jan Engelhardt | 0cb47ea | 2010-03-16 18:25:12 +0100 | [diff] [blame] | 356 | --------------------------- |
| 357 | |
| 358 | What: xt_NOTRACK |
| 359 | Files: net/netfilter/xt_NOTRACK.c |
| 360 | When: April 2011 |
| 361 | Why: Superseded by xt_CT |
| 362 | Who: Netfilter developer team <netfilter-devel@vger.kernel.org> |
David S. Miller | 278554b | 2010-05-12 00:05:35 -0700 | [diff] [blame] | 363 | |
Linus Torvalds | 6e0b7b2 | 2010-05-19 17:09:40 -0700 | [diff] [blame] | 364 | ---------------------------- |
| 365 | |
Thomas Gleixner | 6932bf3 | 2010-03-26 00:06:55 +0000 | [diff] [blame] | 366 | What: IRQF_DISABLED |
| 367 | When: 2.6.36 |
| 368 | Why: The flag is a NOOP as we run interrupt handlers with interrupts disabled |
| 369 | Who: Thomas Gleixner <tglx@linutronix.de> |
Linus Torvalds | 6e0b7b2 | 2010-05-19 17:09:40 -0700 | [diff] [blame] | 370 | |
| 371 | ---------------------------- |
| 372 | |
FUJITA Tomonori | 1758336 | 2010-08-10 18:03:26 -0700 | [diff] [blame] | 373 | What: PCI DMA unmap state API |
| 374 | When: August 2012 |
| 375 | Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced |
| 376 | with DMA unmap state API (DMA unmap state API can be used for |
| 377 | any bus). |
| 378 | Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> |
| 379 | |
| 380 | ---------------------------- |
FUJITA Tomonori | a35274c | 2010-08-10 18:03:26 -0700 | [diff] [blame] | 381 | |
Wey-Yi Guy | 72645ef | 2010-10-06 07:42:43 -0700 | [diff] [blame] | 382 | What: iwlwifi disable_hw_scan module parameters |
Deepak Saxena | d5b55a8 | 2011-06-09 15:03:03 -0700 | [diff] [blame] | 383 | When: 3.0 |
Wey-Yi Guy | 72645ef | 2010-10-06 07:42:43 -0700 | [diff] [blame] | 384 | Why: Hareware scan is the prefer method for iwlwifi devices for |
| 385 | scanning operation. Remove software scan support for all the |
| 386 | iwlwifi devices. |
| 387 | |
| 388 | Who: Wey-Yi Guy <wey-yi.w.guy@intel.com> |
| 389 | |
| 390 | ---------------------------- |
Linus Torvalds | 4390110 | 2010-10-26 09:55:25 -0700 | [diff] [blame] | 391 | |
Jean Delvare | 632bdb2 | 2011-01-12 21:55:10 +0100 | [diff] [blame] | 392 | What: Legacy, non-standard chassis intrusion detection interface. |
| 393 | When: June 2011 |
| 394 | Why: The adm9240, w83792d and w83793 hardware monitoring drivers have |
| 395 | legacy interfaces for chassis intrusion detection. A standard |
| 396 | interface has been added to each driver, so the legacy interface |
| 397 | can be removed. |
| 398 | Who: Jean Delvare <khali@linux-fr.org> |
| 399 | |
| 400 | ---------------------------- |
Michal Hocko | 552b372 | 2011-02-01 15:52:31 -0800 | [diff] [blame] | 401 | |
Jean Delvare | fe6fc25 | 2011-03-20 14:50:53 +0100 | [diff] [blame] | 402 | What: i2c_driver.attach_adapter |
| 403 | i2c_driver.detach_adapter |
| 404 | When: September 2011 |
| 405 | Why: These legacy callbacks should no longer be used as i2c-core offers |
| 406 | a variety of preferable alternative ways to instantiate I2C devices. |
| 407 | Who: Jean Delvare <khali@linux-fr.org> |
| 408 | |
| 409 | ---------------------------- |
Laurent Pinchart | 1dc8ddf | 2010-10-12 12:11:30 -0300 | [diff] [blame] | 410 | |
Hans Verkuil | 6293698 | 2011-06-13 09:38:54 -0300 | [diff] [blame] | 411 | What: Opening a radio device node will no longer automatically switch the |
| 412 | tuner mode from tv to radio. |
| 413 | When: 3.3 |
| 414 | Why: Just opening a V4L device should not change the state of the hardware |
| 415 | like that. It's very unexpected and against the V4L spec. Instead, you |
| 416 | switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second |
| 417 | and last step of the move to consistent handling of tv and radio tuners. |
| 418 | Who: Hans Verkuil <hans.verkuil@cisco.com> |
| 419 | |
| 420 | ---------------------------- |
Linus Torvalds | f549953 | 2011-07-25 23:08:32 -0700 | [diff] [blame] | 421 | |
Johannes Berg | 10bab00 | 2012-05-16 23:40:19 +0200 | [diff] [blame] | 422 | What: CONFIG_CFG80211_WEXT |
| 423 | When: as soon as distributions ship new wireless tools, ie. wpa_supplicant 1.0 |
| 424 | and NetworkManager/connman/etc. that are able to use nl80211 |
| 425 | Why: Wireless extensions are deprecated, and userland tools are moving to |
| 426 | using nl80211. New drivers are no longer using wireless extensions, |
| 427 | and while there might still be old drivers, both new drivers and new |
| 428 | userland no longer needs them and they can't be used for an feature |
| 429 | developed in the past couple of years. As such, compatibility with |
| 430 | wireless extensions in new drivers will be removed. |
| 431 | Who: Johannes Berg <johannes@sipsolutions.net> |
| 432 | |
| 433 | ---------------------------- |
| 434 | |
Alan Stern | 664a51a | 2011-06-15 16:31:37 -0400 | [diff] [blame] | 435 | What: g_file_storage driver |
| 436 | When: 3.8 |
| 437 | Why: This driver has been superseded by g_mass_storage. |
| 438 | Who: Alan Stern <stern@rowland.harvard.edu> |
| 439 | |
| 440 | ---------------------------- |
Lee, Chun-Yi | 7b8aca6 | 2011-05-31 14:52:22 +0800 | [diff] [blame] | 441 | |
| 442 | What: threeg and interface sysfs files in /sys/devices/platform/acer-wmi |
| 443 | When: 2012 |
| 444 | Why: In 3.0, we can now autodetect internal 3G device and already have |
| 445 | the threeg rfkill device. So, we plan to remove threeg sysfs support |
| 446 | for it's no longer necessary. |
| 447 | |
| 448 | We also plan to remove interface sysfs file that exposed which ACPI-WMI |
| 449 | interface that was used by acer-wmi driver. It will replaced by |
| 450 | information log when acer-wmi initial. |
| 451 | Who: Lee, Chun-Yi <jlee@novell.com> |
Christoph Hellwig | 242d621 | 2011-08-24 05:57:51 +0000 | [diff] [blame] | 452 | |
Michal Nazarewicz | d327ab5 | 2011-11-19 18:27:37 +0100 | [diff] [blame] | 453 | --------------------------- |
| 454 | |
| 455 | What: /sys/devices/platform/_UDC_/udc/_UDC_/is_dualspeed file and |
| 456 | is_dualspeed line in /sys/devices/platform/ci13xxx_*/udc/device file. |
| 457 | When: 3.8 |
| 458 | Why: The is_dualspeed file is superseded by maximum_speed in the same |
| 459 | directory and is_dualspeed line in device file is superseded by |
| 460 | max_speed line in the same file. |
| 461 | |
| 462 | The maximum_speed/max_speed specifies maximum speed supported by UDC. |
| 463 | To check if dualspeeed is supported, check if the value is >= 3. |
| 464 | Various possible speeds are defined in <linux/usb/ch9.h>. |
| 465 | Who: Michal Nazarewicz <mina86@mina86.com> |
| 466 | |
Christoph Hellwig | 242d621 | 2011-08-24 05:57:51 +0000 | [diff] [blame] | 467 | ---------------------------- |
John W. Linville | 094daf7 | 2011-10-11 15:35:42 -0400 | [diff] [blame] | 468 | |
Christoph Hellwig | 242d621 | 2011-08-24 05:57:51 +0000 | [diff] [blame] | 469 | What: The XFS nodelaylog mount option |
| 470 | When: 3.3 |
| 471 | Why: The delaylog mode that has been the default since 2.6.39 has proven |
| 472 | stable, and the old code is in the way of additional improvements in |
| 473 | the log code. |
| 474 | Who: Christoph Hellwig <hch@lst.de> |
John W. Linville | 094daf7 | 2011-10-11 15:35:42 -0400 | [diff] [blame] | 475 | |
| 476 | ---------------------------- |
| 477 | |
Don Fry | 3c607d2 | 2011-09-30 11:40:20 -0700 | [diff] [blame] | 478 | What: iwlagn alias support |
| 479 | When: 3.5 |
| 480 | Why: The iwlagn module has been renamed iwlwifi. The alias will be around |
| 481 | for backward compatibility for several cycles and then dropped. |
John W. Linville | 094daf7 | 2011-10-11 15:35:42 -0400 | [diff] [blame] | 482 | Who: Don Fry <donald.h.fry@intel.com> |
Bjorn Helgaas | 7e00fe2 | 2011-10-28 16:26:05 -0600 | [diff] [blame] | 483 | |
| 484 | ---------------------------- |
| 485 | |
| 486 | What: pci_scan_bus_parented() |
| 487 | When: 3.5 |
| 488 | Why: The pci_scan_bus_parented() interface creates a new root bus. The |
| 489 | bus is created with default resources (ioport_resource and |
| 490 | iomem_resource) that are always wrong, so we rely on arch code to |
| 491 | correct them later. Callers of pci_scan_bus_parented() should |
| 492 | convert to using pci_scan_root_bus() so they can supply a list of |
| 493 | bus resources when the bus is created. |
| 494 | Who: Bjorn Helgaas <bhelgaas@google.com> |
Nicolas Ferre | 08a52e1 | 2012-01-06 16:09:37 +0100 | [diff] [blame] | 495 | |
| 496 | ---------------------------- |
| 497 | |
Kees Cook | ec0c427 | 2012-03-23 12:08:55 -0700 | [diff] [blame] | 498 | What: get_robust_list syscall |
| 499 | When: 2013 |
| 500 | Why: There appear to be no production users of the get_robust_list syscall, |
| 501 | and it runs the risk of leaking address locations, allowing the bypass |
| 502 | of ASLR. It was only ever intended for debugging, so it should be |
| 503 | removed. |
| 504 | Who: Kees Cook <keescook@chromium.org> |
Linus Torvalds | ccb1ec9 | 2012-04-12 15:16:26 -0700 | [diff] [blame] | 505 | |
| 506 | ---------------------------- |
| 507 | |
Samuel Ortiz | 4333459 | 2012-05-07 12:31:30 +0200 | [diff] [blame] | 508 | What: Removing the pn544 raw driver. |
| 509 | When: 3.6 |
| 510 | Why: With the introduction of the NFC HCI and SHDL kernel layers, pn544.c |
| 511 | is being replaced by pn544_hci.c which is accessible through the netlink |
| 512 | and socket NFC APIs. Moreover, pn544.c is outdated and does not seem to |
| 513 | work properly with the latest Android stacks. |
| 514 | Having 2 drivers for the same hardware is confusing and as such we |
| 515 | should only keep the one following the kernel NFC APIs. |
| 516 | Who: Samuel Ortiz <sameo@linux.intel.com> |
| 517 | |
| 518 | ---------------------------- |
| 519 | |
Sasikantha babu | aa2bf9b | 2012-03-21 20:10:54 +0530 | [diff] [blame] | 520 | What: setitimer accepts user NULL pointer (value) |
| 521 | When: 3.6 |
| 522 | Why: setitimer is not returning -EFAULT if user pointer is NULL. This |
| 523 | violates the spec. |
| 524 | Who: Sasikantha Babu <sasikanth.v19@gmail.com> |
Sylwester Nawrocki | 5694e02 | 2012-04-21 14:11:06 -0300 | [diff] [blame] | 525 | |
| 526 | ---------------------------- |
| 527 | |
Hans Verkuil | f2b9e8a | 2012-04-24 10:30:15 -0300 | [diff] [blame] | 528 | What: remove bogus DV presets V4L2_DV_1080I29_97, V4L2_DV_1080I30 and |
| 529 | V4L2_DV_1080I25 |
| 530 | When: 3.6 |
| 531 | Why: These HDTV formats do not exist and were added by a confused mind |
| 532 | (that was me, to be precise...) |
| 533 | Who: Hans Verkuil <hans.verkuil@cisco.com> |
| 534 | |
| 535 | ---------------------------- |
| 536 | |
Sylwester Nawrocki | 5694e02 | 2012-04-21 14:11:06 -0300 | [diff] [blame] | 537 | What: V4L2_CID_HCENTER, V4L2_CID_VCENTER V4L2 controls |
| 538 | When: 3.7 |
| 539 | Why: The V4L2_CID_VCENTER, V4L2_CID_HCENTER controls have been deprecated |
| 540 | for about 4 years and they are not used by any mainline driver. |
| 541 | There are newer controls (V4L2_CID_PAN*, V4L2_CID_TILT*) that provide |
| 542 | similar functionality. |
| 543 | Who: Sylwester Nawrocki <sylvester.nawrocki@gmail.com> |
Linus Torvalds | 88d6ae8d | 2012-05-22 17:40:19 -0700 | [diff] [blame] | 544 | |
| 545 | ---------------------------- |
| 546 | |
Tejun Heo | 8b5a5a9 | 2012-04-01 12:09:54 -0700 | [diff] [blame] | 547 | What: cgroup option updates via remount |
| 548 | When: March 2013 |
| 549 | Why: Remount currently allows changing bound subsystems and |
| 550 | release_agent. Rebinding is hardly useful as it only works |
| 551 | when the hierarchy is empty and release_agent itself should be |
| 552 | replaced with conventional fsnotify. |
Linus Torvalds | 88d6ae8d | 2012-05-22 17:40:19 -0700 | [diff] [blame] | 553 | |
| 554 | ---------------------------- |
Linus Torvalds | 07acfc2 | 2012-05-24 16:17:30 -0700 | [diff] [blame] | 555 | |
Denys Fedoryshchenko | efdedd5 | 2012-05-17 23:08:57 +0300 | [diff] [blame] | 556 | What: xt_recent rev 0 |
| 557 | When: 2013 |
| 558 | Who: Pablo Neira Ayuso <pablo@netfilter.org> |
| 559 | Files: net/netfilter/xt_recent.c |
| 560 | |
| 561 | ---------------------------- |
| 562 | |
Avi Kivity | 66ef893 | 2012-04-08 12:47:32 +0300 | [diff] [blame] | 563 | What: KVM debugfs statistics |
| 564 | When: 2013 |
| 565 | Why: KVM tracepoints provide mostly equivalent information in a much more |
| 566 | flexible fashion. |
Marcelo Tosatti | eac0556 | 2012-04-19 17:06:26 -0300 | [diff] [blame] | 567 | |
Linus Torvalds | 07acfc2 | 2012-05-24 16:17:30 -0700 | [diff] [blame] | 568 | ---------------------------- |
Linus Torvalds | 92bf3d0 | 2012-05-25 08:23:32 -0700 | [diff] [blame] | 569 | |
Ludovic Desroches | 0caaa95 | 2012-05-16 17:51:59 +0200 | [diff] [blame] | 570 | What: at91-mci driver ("CONFIG_MMC_AT91") |
| 571 | When: 3.7 |
| 572 | Why: There are two mci drivers: at91-mci and atmel-mci. The PDC support |
| 573 | was added to atmel-mci as a first step to support more chips. |
| 574 | Then at91-mci was kept only for old IP versions (on at91rm9200 and |
| 575 | at91sam9261). The support of these IP versions has just been added |
| 576 | to atmel-mci, so atmel-mci can be used for all chips. |
| 577 | Who: Ludovic Desroches <ludovic.desroches@atmel.com> |
Linus Torvalds | 92bf3d0 | 2012-05-25 08:23:32 -0700 | [diff] [blame] | 578 | |
| 579 | ---------------------------- |
Linus Torvalds | 13199a0 | 2012-05-31 10:32:36 -0700 | [diff] [blame] | 580 | |
Joe Perches | f0d1b3c | 2012-05-24 07:13:30 +0000 | [diff] [blame] | 581 | What: net/wanrouter/ |
| 582 | When: June 2013 |
| 583 | Why: Unsupported/unmaintained/unused since 2.6 |
| 584 | |
| 585 | ---------------------------- |
Linus Torvalds | 6df419e | 2012-07-30 19:03:41 -0700 | [diff] [blame] | 586 | |
Sylwester Nawrocki | 6889d5c | 2012-06-25 16:14:41 -0300 | [diff] [blame] | 587 | What: V4L2 selections API target rectangle and flags unification, the |
| 588 | following definitions will be removed: V4L2_SEL_TGT_CROP_ACTIVE, |
| 589 | V4L2_SEL_TGT_COMPOSE_ACTIVE, V4L2_SUBDEV_SEL_*, V4L2_SUBDEV_SEL_FLAG_* |
| 590 | in favor of common V4L2_SEL_TGT_* and V4L2_SEL_FLAG_* definitions. |
| 591 | For more details see include/linux/v4l2-common.h. |
| 592 | When: 3.8 |
| 593 | Why: The regular V4L2 selections and the subdev selection API originally |
| 594 | defined distinct names for the target rectangles and flags - V4L2_SEL_* |
| 595 | and V4L2_SUBDEV_SEL_*. Although, it turned out that the meaning of these |
| 596 | target rectangles is virtually identical and the APIs were consolidated |
| 597 | to use single set of names - V4L2_SEL_*. This didn't involve any ABI |
| 598 | changes. Alias definitions were created for the original ones to avoid |
| 599 | any instabilities in the user space interface. After few cycles these |
| 600 | backward compatibility definitions will be removed. |
| 601 | Who: Sylwester Nawrocki <sylvester.nawrocki@gmail.com> |
Linus Torvalds | 6df419e | 2012-07-30 19:03:41 -0700 | [diff] [blame] | 602 | |
| 603 | ---------------------------- |
Sylwester Nawrocki | a1367f1 | 2012-07-26 09:30:50 -0300 | [diff] [blame] | 604 | |
| 605 | What: Using V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags |
| 606 | to indicate a V4L2 memory-to-memory device capability |
| 607 | When: 3.8 |
| 608 | Why: New drivers should use new V4L2_CAP_VIDEO_M2M capability flag |
| 609 | to indicate a V4L2 video memory-to-memory (M2M) device and |
| 610 | applications can now identify a M2M video device by checking |
| 611 | for V4L2_CAP_VIDEO_M2M, with VIDIOC_QUERYCAP ioctl. Using ORed |
| 612 | V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags for M2M |
| 613 | devices is ambiguous and may lead, for example, to identifying |
| 614 | a M2M device as a video capture or output device. |
| 615 | Who: Sylwester Nawrocki <s.nawrocki@samsung.com> |
Linus Torvalds | 8762541 | 2012-07-31 18:47:44 -0700 | [diff] [blame] | 616 | |
| 617 | ---------------------------- |
Linus Torvalds | a6dc772 | 2012-08-01 16:41:07 -0700 | [diff] [blame] | 618 | |
Russell King | 4e1755b | 2012-04-23 16:52:29 +0100 | [diff] [blame] | 619 | What: OMAP private DMA implementation |
| 620 | When: 2013 |
| 621 | Why: We have a DMA engine implementation; all users should be updated |
| 622 | to use this rather than persisting with the old APIs. The old APIs |
| 623 | block merging the old DMA engine implementation into the DMA |
| 624 | engine driver. |
| 625 | Who: Russell King <linux@arm.linux.org.uk>, |
| 626 | Santosh Shilimkar <santosh.shilimkar@ti.com> |
| 627 | |
| 628 | ---------------------------- |