From: Dave Jones Despite repeated attempts over the last two and half years, this driver seems somewhat persistant. Remove its deprecated status as it has existing users who may not be in a position to migrate their apps to O_DIRECT. Signed-off-by: Dave Jones Signed-off-by: Andrew Morton --- Documentation/feature-removal-schedule.txt | 8 -------- drivers/char/Kconfig | 9 ++++----- 2 files changed, 4 insertions(+), 13 deletions(-) diff -puN Documentation/feature-removal-schedule.txt~undeprecate-raw-driver Documentation/feature-removal-schedule.txt --- a/Documentation/feature-removal-schedule.txt~undeprecate-raw-driver +++ a/Documentation/feature-removal-schedule.txt @@ -41,14 +41,6 @@ Who: Pavel Machek --------------------------- -What: RAW driver (CONFIG_RAW_DRIVER) -When: December 2005 -Why: declared obsolete since kernel 2.6.3 - O_DIRECT can be used instead -Who: Adrian Bunk - ---------------------------- - What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN When: June 2007 Why: Deprecated in favour of the more efficient and robust rawiso interface. diff -puN drivers/char/Kconfig~undeprecate-raw-driver drivers/char/Kconfig --- a/drivers/char/Kconfig~undeprecate-raw-driver +++ a/drivers/char/Kconfig @@ -978,15 +978,14 @@ config GPIO_VR41XX depends on CPU_VR41XX config RAW_DRIVER - tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)" + tristate "RAW driver (/dev/raw/rawN)" depends on BLOCK help - The raw driver permits block devices to be bound to /dev/raw/rawN. - Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. + The raw driver permits block devices to be bound to /dev/raw/rawN. + Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. See the raw(8) manpage for more details. - The raw driver is deprecated and will be removed soon. - Applications should simply open the device (eg /dev/hda1) + Applications should preferably open the device (eg /dev/hda1) with the O_DIRECT flag. config MAX_RAW_DEVS _