Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq

[sfrench/cifs-2.6.git] / Documentation / feature-removal-schedule.txt

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 79cb554761afb18fab2b2d0023b246a1324e46f4..9699157c25c88ef1fd55c0b4eccb93ac1c6060a9 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -377,16 +377,6 @@ Who:       Eric Paris <eparis@redhat.com>
 
 ----------------------------
 
-What:  lock_policy_rwsem_* and unlock_policy_rwsem_* will not be
-       exported interface anymore.
-When:  2.6.33
-Why:   cpu_policy_rwsem has a new cleaner definition making it local to
-       cpufreq core and contained inside cpufreq.c. Other dependent
-       drivers should not use it in order to safely avoid lockdep issues.
-Who:   Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
-
-----------------------------
-
 What:  sound-slot/service-* module aliases and related clutters in
        sound/sound_core.c
 When:  August 2010
@@ -487,17 +477,6 @@ Who:       Jan Kiszka <jan.kiszka@web.de>
 
 ----------------------------
 
-What:  KVM memory aliases support
-When:  July 2010
-Why:   Memory aliasing support is used for speeding up guest vga access
-       through the vga windows.
-
-       Modern userspace no longer uses this feature, so it's just bitrotted
-       code and can be removed with no impact.
-Who:   Avi Kivity <avi@redhat.com>
-
-----------------------------
-
 What:  xtime, wall_to_monotonic
 When:  2.6.36+
 Files: kernel/time/timekeeping.c include/linux/time.h
@@ -508,16 +487,6 @@ Who:       John Stultz <johnstul@us.ibm.com>
 
 ----------------------------
 
-What:  KVM kernel-allocated memory slots
-When:  July 2010
-Why:   Since 2.6.25, kvm supports user-allocated memory slots, which are
-       much more flexible than kernel-allocated slots.  All current userspace
-       supports the newer interface and this code can be removed with no
-       impact.
-Who:   Avi Kivity <avi@redhat.com>
-
-----------------------------
-
 What:  KVM paravirt mmu host support
 When:  January 2011
 Why:   The paravirt mmu host support is slower than non-paravirt mmu, both