From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Frank Davis <fdavis@andrew.cmu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [CFT] dmfe.c network driver update for 2.4
Date: Sat, 18 Nov 2000 19:10:58 -0500 [thread overview]
Message-ID: <3A171A92.18FF3C3E@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011190100250.24779-100000@svea.tellus>
Tobias Ringstrom wrote:
>
> On Fri, 17 Nov 2000, Frank Davis wrote:
> >
> > I would rather fix those non-SMP compliant drivers to be SMP compliant,
> > then keeping them 'broken'. Adding the print statements would only be a
> > temporary solution.
>
> Of course. This list of priorites is very natural, I think:
>
> 1. Working SMP driver
> 2. Broken SMP driver with a warning.
> 3. Broken SMP driver without a warning. (Even if "everyone" knows it
> is broken)
>
> It takes less than a minute to add such a warning, but it can take days
> or weeks to find someone to really fix the driver. That was my point.
Marking them with a #warning is fine with me.
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-19 0:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 20:34 [CFT] dmfe.c network driver update for 2.4 Tobias Ringstrom
2000-11-15 20:49 ` Frank Davis
2000-11-15 22:21 ` Jeff Garzik
2000-11-16 21:50 ` Tobias Ringstrom
2000-11-16 21:56 ` Jeff Garzik
2000-11-17 9:20 ` Tobias Ringstrom
2000-11-17 22:28 ` Frank Davis
2000-11-17 22:30 ` Jeff Garzik
2000-11-19 0:05 ` Tobias Ringstrom
2000-11-19 0:10 ` Jeff Garzik [this message]
2000-11-21 13:42 ` Peter Samuelson
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=3A171A92.18FF3C3E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=fdavis@andrew.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.