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.txt22
1 files changed, 22 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 7279595b96c3..9119d037c2ce 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -172,6 +172,16 @@ Who: Len Brown <len.brown@intel.com>
172 172
173--------------------------- 173---------------------------
174 174
175What: ide-tape driver
176When: July 2008
177Files: drivers/ide/ide-tape.c
178Why: This driver might not have any users anymore and maintaining it for no
179 reason is an effort no one wants to make.
180Who: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>, Borislav Petkov
181 <petkovbb@googlemail.com>
182
183---------------------------
184
175What: libata spindown skipping and warning 185What: libata spindown skipping and warning
176When: Dec 2008 186When: Dec 2008
177Why: Some halt(8) implementations synchronize caches for and spin 187Why: Some halt(8) implementations synchronize caches for and spin
@@ -279,3 +289,15 @@ Why: Largely unmaintained and almost entirely unused. File system
279 is largely pointless as without a lot of work only the most 289 is largely pointless as without a lot of work only the most
280 trivial of Solaris binaries can work with the emulation code. 290 trivial of Solaris binaries can work with the emulation code.
281Who: David S. Miller <davem@davemloft.net> 291Who: David S. Miller <davem@davemloft.net>
292
293---------------------------
294
295What: init_mm export
296When: 2.6.26
297Why: Not used in-tree. The current out-of-tree users used it to
298 work around problems in the CPA code which should be resolved
299 by now. One usecase was described to provide verification code
300 of the CPA operation. That's a good idea in general, but such
301 code / infrastructure should be in the kernel and not in some
302 out-of-tree driver.
303Who: Thomas Gleixner <tglx@linutronix.de>