The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: arjan@infradead.org, bunk@stusta.de,
	linux-kernel@vger.kernel.org, pbadari@us.ibm.com,
	kenneth.w.chen@intel.com
Subject: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
Date: Sat, 21 Jan 2006 13:17:18 -0800	[thread overview]
Message-ID: <20060121131718.1b6bbcdc.akpm@osdl.org> (raw)
In-Reply-To: <20060121194102.GB28051@redhat.com>

Dave Jones <davej@redhat.com> wrote:
>
> On Sat, Jan 21, 2006 at 09:52:27AM +0100, Arjan van de Ven wrote:
>  > On Wed, 2006-01-18 at 19:41 -0800, Andrew Morton wrote:
>  > > Adrian Bunk <bunk@stusta.de> wrote:
>  > > >
>  > > > Let's do the scheduled removal of the obsolete raw driver in 2.6.17.
>  > > > 
>  > > 
>  > > heh.  I was just thinking that I hadn't heard from Badari and Ken in a while.
>  > > 
>  > > I doubt if this'll fly.  We're stuck with it.
>  > 
>  > One thing we can do is ask the distributions to stop shipping raw first,
>  > to see what the fallout is (and to give it as a sign that it's an
>  > obsolete interface). Then a  year or two after that....
> 
> It's been off in Fedora since FC4.
> RHEL4 had it enabled after several vendors complained a lot about its
> absense breaking an installed userbase, though they were told it would be
> enabled with the proviso that it would go away in the future.
> RHEL5 isn't even in beta yet, but I can already hear the voices asking
> for it be reenabled..
> 

Thanks for trying though ;) It's good that RH is helping to push things
along like this - the easiest path would be to turn the thing on and
complain when anyone made noises about taking it out.


  reply	other threads:[~2006-01-21 21:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  3:02 [2.6 patch] the scheduled removal of the obsolete raw driver Adrian Bunk
2006-01-19  3:41 ` Andrew Morton
2006-01-19  5:43   ` Chen, Kenneth W
2006-01-21  1:02     ` Adrian Bunk
2006-01-21  1:08       ` Chen, Kenneth W
2006-01-21  1:49       ` Alan Cox
2006-01-19 16:10   ` Adrian Bunk
2006-01-19 16:44   ` Badari Pulavarty
2006-01-19 16:52     ` Mark Lord
2006-01-19 16:58     ` Adrian Bunk
2006-01-19 18:14       ` Badari Pulavarty
2006-01-20  8:24       ` [SARCASM] " Ingo Oeser
2006-01-20 14:02         ` Jan Engelhardt
2006-01-22 12:51       ` [OT] " Alexander E. Patrakov
2006-01-21  8:52   ` Arjan van de Ven
2006-01-21 19:41     ` Dave Jones
2006-01-21 21:17       ` Andrew Morton [this message]
2006-01-21 21:25         ` Arjan van de Ven
2006-01-21 21:35           ` Andrew Morton
2006-01-21 21:50             ` Arjan van de Ven
2006-01-22 17:50             ` Jesper Juhl
2006-01-21 23:26 ` Gene Heskett
2006-01-21 23:30   ` Lee Revell
2006-01-21 23:53     ` Gene Heskett
2006-01-21 23:59       ` Doug McNaught
2006-01-22  0:09         ` Gene Heskett
2006-01-22  0:15           ` Lee Revell
2006-01-22  1:30             ` Doug McNaught
2006-01-22  8:14           ` Arjan van de Ven
2006-01-22 20:33         ` Alan Cox
2006-01-22 21:53           ` Jan Engelhardt

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=20060121131718.1b6bbcdc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /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