aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt91
1 files changed, 0 insertions, 91 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 40a9c323931..be7030e4dd7 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -303,15 +303,6 @@ Who: Johannes Berg <johannes@sipsolutions.net>
303 303
304--------------------------- 304---------------------------
305 305
306What: CONFIG_NF_CT_ACCT
307When: 2.6.29
308Why: Accounting can now be enabled/disabled without kernel recompilation.
309 Currently used only to set a default value for a feature that is also
310 controlled by a kernel/module/sysfs/sysctl parameter.
311Who: Krzysztof Piotr Oledzki <ole@ans.pl>
312
313---------------------------
314
315What: sysfs ui for changing p4-clockmod parameters 306What: sysfs ui for changing p4-clockmod parameters
316When: September 2009 307When: September 2009
317Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and 308Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
@@ -377,16 +368,6 @@ Who: Eric Paris <eparis@redhat.com>
377 368
378---------------------------- 369----------------------------
379 370
380What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be
381 exported interface anymore.
382When: 2.6.33
383Why: cpu_policy_rwsem has a new cleaner definition making it local to
384 cpufreq core and contained inside cpufreq.c. Other dependent
385 drivers should not use it in order to safely avoid lockdep issues.
386Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
387
388----------------------------
389
390What: sound-slot/service-* module aliases and related clutters in 371What: sound-slot/service-* module aliases and related clutters in
391 sound/sound_core.c 372 sound/sound_core.c
392When: August 2010 373When: August 2010
@@ -459,57 +440,6 @@ Who: Corentin Chary <corentin.chary@gmail.com>
459 440
460---------------------------- 441----------------------------
461 442
462What: usbvideo quickcam_messenger driver
463When: 2.6.35
464Files: drivers/media/video/usbvideo/quickcam_messenger.[ch]
465Why: obsolete v4l1 driver replaced by gspca_stv06xx
466Who: Hans de Goede <hdegoede@redhat.com>
467
468----------------------------
469
470What: ov511 v4l1 driver
471When: 2.6.35
472Files: drivers/media/video/ov511.[ch]
473Why: obsolete v4l1 driver replaced by gspca_ov519
474Who: Hans de Goede <hdegoede@redhat.com>
475
476----------------------------
477
478What: w9968cf v4l1 driver
479When: 2.6.35
480Files: drivers/media/video/w9968cf*.[ch]
481Why: obsolete v4l1 driver replaced by gspca_ov519
482Who: Hans de Goede <hdegoede@redhat.com>
483
484----------------------------
485
486What: ovcamchip sensor framework
487When: 2.6.35
488Files: drivers/media/video/ovcamchip/*
489Why: Only used by obsoleted v4l1 drivers
490Who: Hans de Goede <hdegoede@redhat.com>
491
492----------------------------
493
494What: stv680 v4l1 driver
495When: 2.6.35
496Files: drivers/media/video/stv680.[ch]
497Why: obsolete v4l1 driver replaced by gspca_stv0680
498Who: Hans de Goede <hdegoede@redhat.com>
499
500----------------------------
501
502What: zc0301 v4l driver
503When: 2.6.35
504Files: drivers/media/video/zc0301/*
505Why: Duplicate functionality with the gspca_zc3xx driver, zc0301 only
506 supports 2 USB-ID's (because it only supports a limited set of
507 sensors) wich are also supported by the gspca_zc3xx driver
508 (which supports 53 USB-ID's in total)
509Who: Hans de Goede <hdegoede@redhat.com>
510
511----------------------------
512
513What: sysfs-class-rfkill state file 443What: sysfs-class-rfkill state file
514When: Feb 2014 444When: Feb 2014
515Files: net/rfkill/core.c 445Files: net/rfkill/core.c
@@ -538,17 +468,6 @@ Who: Jan Kiszka <jan.kiszka@web.de>
538 468
539---------------------------- 469----------------------------
540 470
541What: KVM memory aliases support
542When: July 2010
543Why: Memory aliasing support is used for speeding up guest vga access
544 through the vga windows.
545
546 Modern userspace no longer uses this feature, so it's just bitrotted
547 code and can be removed with no impact.
548Who: Avi Kivity <avi@redhat.com>
549
550----------------------------
551
552What: xtime, wall_to_monotonic 471What: xtime, wall_to_monotonic
553When: 2.6.36+ 472When: 2.6.36+
554Files: kernel/time/timekeeping.c include/linux/time.h 473Files: kernel/time/timekeeping.c include/linux/time.h
@@ -559,16 +478,6 @@ Who: John Stultz <johnstul@us.ibm.com>
559 478
560---------------------------- 479----------------------------
561 480
562What: KVM kernel-allocated memory slots
563When: July 2010
564Why: Since 2.6.25, kvm supports user-allocated memory slots, which are
565 much more flexible than kernel-allocated slots. All current userspace
566 supports the newer interface and this code can be removed with no
567 impact.
568Who: Avi Kivity <avi@redhat.com>
569
570----------------------------
571
572What: KVM paravirt mmu host support 481What: KVM paravirt mmu host support
573When: January 2011 482When: January 2011
574Why: The paravirt mmu host support is slower than non-paravirt mmu, both 483Why: The paravirt mmu host support is slower than non-paravirt mmu, both