public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove the obsolete raw driver
Date: Fri, 20 May 2005 18:25:05 -0700	[thread overview]
Message-ID: <20050521012505.GD2057@holomorphy.com> (raw)
In-Reply-To: <20050521001925.GQ5112@stusta.de>

On Sat, May 21, 2005 at 02:19:25AM +0200, Adrian Bunk wrote:
> Since kernel 2.6.3 the Kconfig text explicitely stated this driver was 
> obsolete.
> It seems to be time to remove it.
> Signed-off-by: Adrian Bunk <bunk@stusta.de>

9 point releases is nowhere long enough. This removal needs to wait for
similar amounts of time as other removed interfaces (c.f. devfs, which
is far more offensive).

In general there are staging rules for this sort of affair, and although
I'm no expert in their fine points, nor can I even say what the exact
criteria are, but it's rather clear in this instance it's over the line.
I suspect a major release, planned as a staging ground for things like
e.g. this and removing devfs, would be the most appropriate time for it.


-- wli

  parent reply	other threads:[~2005-05-21  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21  0:19 [2.6 patch] remove the obsolete raw driver Adrian Bunk
2005-05-21  0:43 ` [2.6 patch] remove the obsolete raw driver] Anton Blanchard
2005-05-21  1:07   ` Jesse Barnes
2005-05-21  0:45 ` [2.6 patch] remove the obsolete raw driver Horst von Brand
2005-05-21 22:47   ` Adrian Bunk
2005-05-21  1:25 ` William Lee Irwin III [this message]
2005-05-21  7:41   ` Adrian Bunk
2005-05-21  7:52     ` William Lee Irwin III
2005-05-21  5:35 ` Greg KH
2005-05-21 11:49   ` Roman Zippel
2005-06-23 10:08   ` [2.6 patch] schedule the obsolete raw driver for removal Adrian Bunk

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=20050521012505.GD2057@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=bunk@stusta.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