diff options
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r-- | Documentation/feature-removal-schedule.txt | 56 |
1 files changed, 48 insertions, 8 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index 3ee1b3b2bfb4..4ab4c425b856 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
@@ -6,6 +6,21 @@ be removed from this file. | |||
6 | 6 | ||
7 | --------------------------- | 7 | --------------------------- |
8 | 8 | ||
9 | What: /sys/devices/.../power/state | ||
10 | dev->power.power_state | ||
11 | dpm_runtime_{suspend,resume)() | ||
12 | When: July 2007 | ||
13 | Why: Broken design for runtime control over driver power states, confusing | ||
14 | driver-internal runtime power management with: mechanisms to support | ||
15 | system-wide sleep state transitions; event codes that distinguish | ||
16 | different phases of swsusp "sleep" transitions; and userspace policy | ||
17 | inputs. This framework was never widely used, and most attempts to | ||
18 | use it were broken. Drivers should instead be exposing domain-specific | ||
19 | interfaces either to kernel or to userspace. | ||
20 | Who: Pavel Machek <pavel@suse.cz> | ||
21 | |||
22 | --------------------------- | ||
23 | |||
9 | What: RAW driver (CONFIG_RAW_DRIVER) | 24 | What: RAW driver (CONFIG_RAW_DRIVER) |
10 | When: December 2005 | 25 | When: December 2005 |
11 | Why: declared obsolete since kernel 2.6.3 | 26 | Why: declared obsolete since kernel 2.6.3 |
@@ -46,6 +61,18 @@ Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br> | |||
46 | 61 | ||
47 | --------------------------- | 62 | --------------------------- |
48 | 63 | ||
64 | What: sys_sysctl | ||
65 | When: January 2007 | ||
66 | Why: The same information is available through /proc/sys and that is the | ||
67 | interface user space prefers to use. And there do not appear to be | ||
68 | any existing user in user space of sys_sysctl. The additional | ||
69 | maintenance overhead of keeping a set of binary names gets | ||
70 | in the way of doing a good job of maintaining this interface. | ||
71 | |||
72 | Who: Eric Biederman <ebiederm@xmission.com> | ||
73 | |||
74 | --------------------------- | ||
75 | |||
49 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) | 76 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
50 | When: November 2005 | 77 | When: November 2005 |
51 | Files: drivers/pcmcia/: pcmcia_ioctl.c | 78 | Files: drivers/pcmcia/: pcmcia_ioctl.c |
@@ -193,14 +220,6 @@ Who: Nick Piggin <npiggin@suse.de> | |||
193 | 220 | ||
194 | --------------------------- | 221 | --------------------------- |
195 | 222 | ||
196 | What: Support for the MIPS EV96100 evaluation board | ||
197 | When: September 2006 | ||
198 | Why: Does no longer build since at least November 15, 2003, apparently | ||
199 | no userbase left. | ||
200 | Who: Ralf Baechle <ralf@linux-mips.org> | ||
201 | |||
202 | --------------------------- | ||
203 | |||
204 | What: Support for the Momentum / PMC-Sierra Jaguar ATX evaluation board | 223 | What: Support for the Momentum / PMC-Sierra Jaguar ATX evaluation board |
205 | When: September 2006 | 224 | When: September 2006 |
206 | Why: Does no longer build since quite some time, and was never popular, | 225 | Why: Does no longer build since quite some time, and was never popular, |
@@ -285,3 +304,24 @@ Why: The frame diverter is included in most distribution kernels, but is | |||
285 | It is not clear if anyone is still using it. | 304 | It is not clear if anyone is still using it. |
286 | Who: Stephen Hemminger <shemminger@osdl.org> | 305 | Who: Stephen Hemminger <shemminger@osdl.org> |
287 | 306 | ||
307 | --------------------------- | ||
308 | |||
309 | |||
310 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment | ||
311 | When: Oktober 2008 | ||
312 | Why: The stacking of class devices makes these values misleading and | ||
313 | inconsistent. | ||
314 | Class devices should not carry any of these properties, and bus | ||
315 | devices have SUBSYTEM and DRIVER as a replacement. | ||
316 | Who: Kay Sievers <kay.sievers@suse.de> | ||
317 | |||
318 | --------------------------- | ||
319 | |||
320 | What: i2c-isa | ||
321 | When: December 2006 | ||
322 | Why: i2c-isa is a non-sense and doesn't fit in the device driver | ||
323 | model. Drivers relying on it are better implemented as platform | ||
324 | drivers. | ||
325 | Who: Jean Delvare <khali@linux-fr.org> | ||
326 | |||
327 | --------------------------- | ||