1 files changed, 27 insertions, 19 deletions

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 99f219a01e0e..87851efb0228 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -55,14 +55,6 @@ Who:	Mauro Carvalho Chehab <mchehab@brturbo.com.br>
 
 ---------------------------
 
-What:   remove EXPORT_SYMBOL(insert_resource)
-When:   April 2006
-Files:  kernel/resource.c
-Why:    No modular usage in the kernel.
-Who:    Adrian Bunk <bunk@stusta.de>
-
----------------------------
-
 What:   PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
 When:   November 2005
 Files:  drivers/pcmcia/: pcmcia_ioctl.c
@@ -166,17 +158,6 @@ Who:	Arjan van de Ven <arjan@linux.intel.com>
 
 ---------------------------
 
-What:   remove EXPORT_SYMBOL(tasklist_lock)
-When:   August 2006
-Files:  kernel/fork.c
-Why:    tasklist_lock protects the kernel internal task list.  Modules have
-        no business looking at it, and all instances in drivers have been due
-        to use of too-lowlevel APIs.  Having this symbol exported prevents
-        moving to more scalable locking schemes for the task list.
-Who:    Christoph Hellwig <hch@lst.de>
-
----------------------------
-
 What:   mount/umount uevents
 When:   February 2007
 Why:    These events are not correct, and do not properly let userspace know
@@ -266,3 +247,30 @@ Why:	The interrupt related SA_* flags are replaced by IRQF_* to move them
 Who:    Thomas Gleixner <tglx@linutronix.de>
 
 ---------------------------
+
+What:   i2c-ite and i2c-algo-ite drivers
+When:   September 2006
+Why:    These drivers never compiled since they were added to the kernel
+        tree 5 years ago. This feature removal can be reevaluated if
+        someone shows interest in the drivers, fixes them and takes over
+        maintenance.
+        http://marc.theaimsgroup.com/?l=linux-mips&m=115040510817448
+Who:    Jean Delvare <khali@linux-fr.org>
+
+---------------------------
+
+What:   Bridge netfilter deferred IPv4/IPv6 output hook calling
+When:   January 2007
+Why:    The deferred output hooks are a layering violation causing unusual
+        and broken behaviour on bridge devices. Examples of things they
+        break include QoS classifation using the MARK or CLASSIFY targets,
+        the IPsec policy match and connection tracking with VLANs on a
+        bridge. Their only use is to enable bridge output port filtering
+        within iptables with the physdev match, which can also be done by
+        combining iptables and ebtables using netfilter marks. Until it
+        will get removed the hook deferral is disabled by default and is
+        only enabled when needed.
+
+Who:    Patrick McHardy <kaber@trash.net>
+
+---------------------------