public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: undeprecate raw driver.
Date: Sun, 13 May 2007 12:43:03 -0400	[thread overview]
Message-ID: <20070513164303.GF27604@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705131835110.9570@yvahk01.tjqt.qr>

On Sun, May 13, 2007 at 06:35:45PM +0200, Jan Engelhardt wrote:

 > >-	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
 > 
 > At least keep the "it's obsolete" Kconfig description. We
 > don't want new users/projects to jump on /dev/raw.

That'll just lead to some janitor sending more "OMG! OBSOLETE!" cleanup
patches getting it re-added to the feature-removal.txt
If we undeprecate it, it won't be going away, so new users of it
aren't any more of a problem than they have been the last two and
a half years.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-05-13 16:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 16:32 undeprecate raw driver Dave Jones
2007-05-13 16:35 ` Jan Engelhardt
2007-05-13 16:43   ` Dave Jones [this message]
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=20070513164303.GF27604@redhat.com \
    --to=davej@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --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