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

El Thu, 24 Jul 2003 13:50:48 -0400 (EDT) "Robert P. J. Day" <rpjday@mindspring.com> escribió:

> 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.

well, AFAIK "make allyesconfig" is a debug target; ie. it 
shouldn't be succesful from a developer point of view.

I guess what you meant is if we want to say to final users
"the driver for your hardware doesn't compile" or "your hardware isn't
supported (unless you're a developer who wants to fix it)" in which case
i'd say "yes"

Or instead, "should make allyesconfig compile drivers marked as obsolete",
where i'd also say "yes"

But sadly i can't fix all those drivers so i'll stop whining and let the real
developers do whatever they want ;)

  reply	other threads:[~2003-07-24 19:01 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
2003-07-24 19:16         ` Diego Calleja García [this message]
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=20030724211611.3f969ae4.diegocg@teleline.es \
    --to=diegocg@teleline.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ml@basmevissen.nl \
    --cc=rpjday@mindspring.com \
    --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).