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.txt38
1 files changed, 27 insertions, 11 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 144058cf849a..5f96cb33743e 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -183,18 +183,10 @@ Who: Jean Delvare <khali@linux-fr.org>
183 183
184--------------------------- 184---------------------------
185 185
186What: i2c_adapter.dev 186What: i2c_adapter.list
187 i2c_adapter.list
188When: July 2007 187When: July 2007
189Why: Superfluous, given i2c_adapter.class_dev: 188Why: Superfluous, this list duplicates the one maintained by the driver
190 * The "dev" was a stand-in for the physical device node that legacy 189 core.
191 drivers would not have; but now it's almost always present. Any
192 remaining legacy drivers must upgrade (they now trigger warnings).
193 * The "list" duplicates class device children.
194 The delay in removing this is so upgraded lm_sensors and libsensors
195 can get deployed. (Removal causes minor changes in the sysfs layout,
196 notably the location of the adapter type name and parenting the i2c
197 client hardware directly from their controller.)
198Who: Jean Delvare <khali@linux-fr.org>, 190Who: Jean Delvare <khali@linux-fr.org>,
199 David Brownell <dbrownell@users.sourceforge.net> 191 David Brownell <dbrownell@users.sourceforge.net>
200 192
@@ -307,3 +299,27 @@ Why: Code was merged, then submitter immediately disappeared leaving
307Who: David S. Miller <davem@davemloft.net> 299Who: David S. Miller <davem@davemloft.net>
308 300
309--------------------------- 301---------------------------
302
303What: read_dev_chars(), read_conf_data{,_lpm}() (s390 common I/O layer)
304When: December 2007
305Why: These functions are a leftover from 2.4 times. They have several
306 problems:
307 - Duplication of checks that are done in the device driver's
308 interrupt handler
309 - common I/O layer can't do device specific error recovery
310 - device driver can't be notified for conditions happening during
311 execution of the function
312 Device drivers should issue the read device characteristics and read
313 configuration data ccws and do the appropriate error handling
314 themselves.
315Who: Cornelia Huck <cornelia.huck@de.ibm.com>
316
317---------------------------
318
319What: i2c-ixp2000, i2c-ixp4xx and scx200_i2c drivers
320When: September 2007
321Why: Obsolete. The new i2c-gpio driver replaces all hardware-specific
322 I2C-over-GPIO drivers.
323Who: Jean Delvare <khali@linux-fr.org>
324
325---------------------------