linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: John Bradford <john@grabjohn.com>
Cc: bunk@fs.tum.de, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org, wowbagger@sktc.net
Subject: Re: time for some drivers to be removed?
Date: Wed, 13 Aug 2003 16:55:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1030813165150.12417J-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <200308132055.h7DKtTkH002249@81-2-122-30.bradfords.org.uk>

On Wed, 13 Aug 2003, John Bradford wrote:

> > > > Interesting question - whatever I guess. We don't have an existing convention.
> > > > How many drivers have we got nowdays that failing on just SMP ?
> > > 
> > > I 2.6.0-test2 tested on i386 with a .config that is without support for
> > > modules and compiles as much as possible statically into the kernel.
> > > Without claiming completeness, I found this way besides the complete Old
> > > ISDN4Linux subsystem 36 drivers that compile due to cli/sti issues only
> > > on UP.
> >
> > Should those be made to depend on SMP (not SMP) perhaps? They are probably
> > high candidates for fixing if they work UP.
> 
> Especially since a lot of the time, 'works on UP, but not on SMP',
> really means, 'broken on UP and SMP, but the bug is much more
> difficult to trigger on UP'.

I was thinking more of not even compiling with SMP set, not so much
compiling but not working. I think that covers the above cli/sti example,
and perhaps there are still drivers which will work built in, but not
compile as modules due to the module redesign.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


  parent reply	other threads:[~2003-08-13 21:16 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 20:55 John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-14  5:34 John Bradford
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-07-28  7:12 linux
2003-07-27 16:22 John Bradford
2003-07-25 11:10 John Bradford
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-24 14:43 John Bradford
2003-07-24 19:24 ` Brian Jackson
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
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

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.3.96.1030813165150.12417J-100000@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wowbagger@sktc.net \
    --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).