linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: bunk@fs.tum.de, john@grabjohn.com
Cc: alan@lxorguk.ukuu.org.uk, davidsen@tmr.com,
	linux-kernel@vger.kernel.org, wowbagger@sktc.net
Subject: Re: time for some drivers to be removed?
Date: Thu, 14 Aug 2003 06:34:04 +0100	[thread overview]
Message-ID: <200308140534.h7E5Y4qc000327@81-2-122-30.bradfords.org.uk> (raw)

> > > > > 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'.
>
> Please reread my mail:
> "that compile due to cli/sti issues only on UP".
>
> This clearly disproves your theory.

I was talking about broken-on-SMP in general, not just this specific
case.

John.

             reply	other threads:[~2003-08-14  5:26 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14  5:34 John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 20:55 time for some drivers to be removed? John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen
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=200308140534.h7E5Y4qc000327@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wowbagger@sktc.net \
    /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;
as well as URLs for NNTP newsgroup(s).