linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: Bas Mevissen <ml@basmevissen.nl>, linux-kernel@vger.kernel.org
Subject: Re: time for some drivers to be removed?
Date: Thu, 24 Jul 2003 13:50:48 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307241346490.20950@localhost.localdomain> (raw)
In-Reply-To: <20030724193211.39d7ed68.diegocg@teleline.es>

On Thu, 24 Jul 2003, Diego Calleja [ISO-8859-15] García wrote:

> El Thu, 24 Jul 2003 17:34:44 +0200 Bas Mevissen <ml@basmevissen.nl> escribió:
> 
> > This would make a reasonable Q-requirement for 2.6.0 that at least the 
> > kernel compiles with 'make allyesconfig'. The only thing open is to 
> 
> That 2.6.0 builds with 'make allyesconfig' or not is irrelevant.
> Moving broken drivers to a dark place doesn't fix them  nor increase the
> "quality" level.....

once upon a time, i suggested having more than one level of module
"quality".  at the moment, some kernel code is marked as "EXPERIMENTAL",
but this is supported via a regular dependency when it doesn't really
qualify as a dependency.  dependencies are typically used to refer to
dependencies on other *code*, not some abstract level of goodness
like "EXPERIMENTAL".

perhaps it's time to add another category with values like OBSOLETE,
DEPRECATED, EXPERIMENTAL, BROKEN(?) and so on.  by default, the
quality would be regular, or something like that.

and in the end, while i know some folks don't think it's a big
deal, i think doing a "make allyesconfig" really should work.

rday

  reply	other threads:[~2003-07-24 17:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 12:20 Robert P. J. Day
2003-07-24 14:58 ` Alan Cox
2003-07-24 15:34   ` Bas Mevissen
2003-07-24 17:32     ` Diego Calleja García
2003-07-24 17:50       ` Robert P. J. Day [this message]
2003-07-24 19:16         ` Diego Calleja García
2003-07-24 19:43           ` Robert P. J. Day
2003-07-24 18:02       ` Samuel Flory
2003-07-24 19:07     ` Alan Cox
2003-07-25 10:48       ` Bas Mevissen
2003-07-27 15:31 ` Adrian Bunk
2003-07-27 15:59   ` David D. Hagood
2003-07-27 16:18     ` Adrian Bunk
2003-07-27 16:40     ` Alan Cox
2003-07-27 17:00       ` Adrian Bunk
2003-07-27 18:45       ` David D. Hagood
2003-07-27 20:40         ` Alan Cox
2003-07-27 20:56           ` Adrian Bunk
2003-07-27 20:56             ` Alan Cox
2003-07-28  2:23               ` Herbert Pötzl
2003-07-29 19:33               ` Adrian Bunk
2003-08-13 20:16                 ` Bill Davidsen
2003-08-09 18:04   ` David Woodhouse
2003-08-09 19:36     ` Adrian Bunk
2003-07-24 14:43 John Bradford
2003-07-24 19:24 ` Brian Jackson
2003-07-24 18:29 John Bradford
2003-07-24 18:31 ` Robert P. J. Day
2003-07-24 19:31   ` Eli Carter
2003-07-25 10:48 ` Bas Mevissen
2003-07-25 11:10 John Bradford
2003-07-27 16:22 John Bradford
2003-07-28  7:12 linux
2003-08-05 12:42 Mikael Pettersson
2003-08-05 13:03 ` Adrian Bunk
2003-08-05 13:35   ` Mikael Pettersson
2003-08-05 13:48     ` Adrian Bunk
2003-08-05 14:01       ` Mikael Pettersson
2003-08-06 10:06         ` Claus-Justus Heine
2003-08-09 19:40           ` Adrian Bunk
2003-08-05 16:35 ` Alan Cox
2003-08-05 18:47   ` Leopold Gouverneur
2003-08-13 20:55 John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen
2003-08-14  5:34 John Bradford

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=Pine.LNX.4.53.0307241346490.20950@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=diegocg@teleline.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ml@basmevissen.nl \
    --subject='Re: time for some drivers to be removed?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).