All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux-Kernel list <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: Caution about e100...
Date: Fri, 08 Mar 2002 03:58:28 -0500	[thread overview]
Message-ID: <3C887D34.4BE740F9@mandrakesoft.com> (raw)

Note to all,

I merged e100 into 2.5.x to get it some wider testing and feedback.  The
driver currently has several PCI posting bugs particularly, and other
outstanding bugs that need zapping before the driver will be considered
stable.

DO NOT USE THIS DRIVER IN PRODUCTION.

After these bugs are fixed and it has received wider testing and
feedback, only then will it be merged into the stable 2.4.x series.

I recommend all vendors avoid this driver, for the moment.  It is for
developers, testers, and early adopters only.  It should be ok for
normal use, but edge cases are not yet zapped.

</PSA>

-- 
Jeff Garzik      | Usenet Rule #2 (John Gilmore): "The Net interprets
Building 1024    | censorship as damage and routes around it."
MandrakeSoft     |

             reply	other threads:[~2002-03-08  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08  8:58 Jeff Garzik [this message]
2002-03-12  1:03 ` Caution about e100 Ken Brownfield

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=3C887D34.4BE740F9@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 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.