mm: remove the leftovers of noswapaccount

[linux-beck.git] / Documentation / feature-removal-schedule.txt

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 72e238465b0b6ca452ee4905dc097007b9ff3dc0..f9d240dfac0695dd547de81d696365ee4207fee7 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -501,16 +501,6 @@ Who:    NeilBrown <neilb@suse.de>
 
 ----------------------------
 
-What:  cancel_rearming_delayed_work[queue]()
-When:  2.6.39
-
-Why:   The functions have been superceded by cancel_delayed_work_sync()
-       quite some time ago.  The conversion is trivial and there is no
-       in-kernel user left.
-Who:   Tejun Heo <tj@kernel.org>
-
-----------------------------
-
 What:  Legacy, non-standard chassis intrusion detection interface.
 When:  June 2011
 Why:   The adm9240, w83792d and w83793 hardware monitoring drivers have
@@ -528,22 +518,6 @@ Files:     net/netfilter/xt_connlimit.c
 
 ----------------------------
 
-What:  noswapaccount kernel command line parameter
-When:  2.6.40
-Why:   The original implementation of memsw feature enabled by
-       CONFIG_CGROUP_MEM_RES_CTLR_SWAP could be disabled by the noswapaccount
-       kernel parameter (introduced in 2.6.29-rc1). Later on, this decision
-       turned out to be not ideal because we cannot have the feature compiled
-       in and disabled by default and let only interested to enable it
-       (e.g. general distribution kernels might need it). Therefore we have
-       added swapaccount[=0|1] parameter (introduced in 2.6.37) which provides
-       the both possibilities. If we remove noswapaccount we will have
-       less command line parameters with the same functionality and we
-       can also cleanup the parameter handling a bit ().
-Who:   Michal Hocko <mhocko@suse.cz>
-
-----------------------------
-
 What:  ipt_addrtype match include file
 When:  2012
 Why:   superseded by xt_addrtype
@@ -583,3 +557,25 @@ Why:       Superseded by the UVCIOC_CTRL_QUERY ioctl.
 Who:   Laurent Pinchart <laurent.pinchart@ideasonboard.com>
 
 ----------------------------
+
+What:  For VIDIOC_S_FREQUENCY the type field must match the device node's type.
+       If not, return -EINVAL.
+When:  3.2
+Why:   It makes no sense to switch the tuner to radio mode by calling
+       VIDIOC_S_FREQUENCY on a video node, or to switch the tuner to tv mode by
+       calling VIDIOC_S_FREQUENCY on a radio node. This is the first step of a
+       move to more consistent handling of tv and radio tuners.
+Who:   Hans Verkuil <hans.verkuil@cisco.com>
+
+----------------------------
+
+What:  Opening a radio device node will no longer automatically switch the
+       tuner mode from tv to radio.
+When:  3.3
+Why:   Just opening a V4L device should not change the state of the hardware
+       like that. It's very unexpected and against the V4L spec. Instead, you
+       switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second
+       and last step of the move to consistent handling of tv and radio tuners.
+Who:   Hans Verkuil <hans.verkuil@cisco.com>
+
+----------------------------