public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: John Bradford <john@grabjohn.com>,
	Riley@Williams.Name, Linux-Kernel@vger.kernel.org
Subject: Re: [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP}
Date: Sat, 2 Aug 2003 21:47:05 +0200	[thread overview]
Message-ID: <20030802194705.GF16426@fs.tum.de> (raw)
In-Reply-To: <20030731091525.GI12849@louise.pinerecords.com>

On Thu, Jul 31, 2003 at 11:15:25AM +0200, Tomas Szepe wrote:
> > [bunk@fs.tum.de]
> > 
> > On Wed, Jul 30, 2003 at 06:04:03PM +0200, Tomas Szepe wrote:
> > > > [bunk@fs.tum.de]
> > > > 
> > > > If a _user_ of a stable kernel notices "it doesn't even compile" this 
> > > > gives a very bad impression of the quality of the Linux kernel.
> > > 
> > > The keyword in this sentence is "stable."
> > > Could you maybe come up with this again at around 2.6.40? :)
> > 
> > The first stable kernel of the 2.6 kernel series will be 2.6.0.
> 
> There are going to be a zillion drivers that don't compile by the
> time 2.6.0 is released, which is precisely when lkml will see a whole
> new wave of people willing to fix things so I really don't think
> hiding the problems behind CONFIG_BROKEN or whatever is reasonable.

Note that we aren't talking about problems that ae easy to fix, such 
problems are already fixed. We are talking about drivers that are broken 
for many months.

Besides this, "a whole new wave of people willing to fix things" isn't
necessarily positive - for several of the broken drivers there were
alredy broken "fixes" posted. Some of these drivers need a non-trivial 
fix by someone who knows what he is doing.

> Tomas Szepe <szepe@pinerecords.com>

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2003-08-02 19:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  9:11 [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP} John Bradford
2003-07-30 10:44 ` Adrian Bunk
2003-07-30 16:04   ` Tomas Szepe
2003-07-30 16:18     ` Adrian Bunk
2003-07-31  9:15       ` Tomas Szepe
2003-08-02 19:47         ` Adrian Bunk [this message]
2003-08-13 14:50         ` Bill Davidsen
2003-08-13 15:31           ` Jeff Garzik
2003-08-13 19:17             ` Adrian Bunk
2003-08-13 21:06             ` Bill Davidsen
2003-08-17  9:39               ` Rob Landley
2003-08-18 23:03                 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-08-17 21:27 John Bradford
2003-08-14  5:28 John Bradford
2003-08-13 20:40 John Bradford
2003-08-13 21:03 ` Adrian Bunk
2003-07-31  9:41 John Bradford
2003-08-02 19:48 ` Adrian Bunk
2003-07-30 11:29 John Bradford
2003-07-30 11:37 ` Adrian Bunk
2003-07-30 11:53   ` Jan Evert van Grootheest
2003-07-29 19:59 Adrian Bunk
2003-07-30  7:44 ` Riley Williams

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=20030802194705.GF16426@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=Riley@Williams.Name \
    --cc=john@grabjohn.com \
    --cc=szepe@pinerecords.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