From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: undeprecate raw driver.
Date: Sun, 13 May 2007 12:32:20 -0400 [thread overview]
Message-ID: <20070513163220.GA31902@redhat.com> (raw)
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 <davej@redhat.com>
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 498ff31..5108619 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -41,14 +41,6 @@ Who: Pavel Machek <pavel@suse.cz>
---------------------------
-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 <bunk@stusta.de>
-
----------------------------
-
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 --git a/drivers/char/Kconfig b/drivers/char/Kconfig
index abcafac..1e4d688 100644
--- a/drivers/char/Kconfig
+++ b/drivers/char/Kconfig
@@ -993,15 +993,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
--
http://www.codemonkey.org.uk
next reply other threads:[~2007-05-13 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 16:32 Dave Jones [this message]
2007-05-13 16:35 ` undeprecate raw driver Jan Engelhardt
2007-05-13 16:43 ` Dave Jones
2007-05-13 16:46 ` Robert P. J. Day
2007-05-13 17:34 ` Bernd Eckenfels
2007-05-13 17:56 ` Robert P. J. Day
2007-05-13 20:06 ` Stefan Richter
2007-05-13 20:24 ` Robert P. J. Day
2007-05-13 21:40 ` Stefan Richter
2007-05-13 20:10 ` Stefan Richter
2007-05-13 21:49 ` Tilman Schmidt
2007-05-13 22:42 ` Stefan Richter
2007-05-13 23:01 ` Bob Johnston
2007-05-14 11:42 ` Alan Cox
2007-05-14 13:53 ` Bob Johnston
2007-05-14 14:07 ` Robert P. J. Day
2007-05-15 2:47 ` David Schwartz
2007-05-14 13:39 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070513163220.GA31902@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox