From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linuxkernel@AdvancedResearch.org (Vincent Stemen)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org,
mikeg@wen-online.de (Mike Galbraith)
Subject: Re: Plain 2.4.5 VM... (and 2.4.5-ac3)
Date: Wed, 30 May 2001 21:11:20 +0100 (BST) [thread overview]
Message-ID: <E155CJM-0006XT-00@the-village.bc.nu> (raw)
In-Reply-To: <01053014585700.01976@quark> from "Vincent Stemen" at May 30, 2001 02:58:57 PM
> There was a new 8139too driver added to the the 2.4.5 (I think) kernel
> which Alan Cox took back out and reverted to the old one in his
> 2.4.5-ac? versions because it is apparently causing lockups.
> Shouldn't this new driver have been released in a 2.5.x development
> kernel and proven there before replacing the one in the production
> kernel? I haven't even seen a 2.5.x kernel released yet.
Nope. The 2.4.3 one is buggy too - but differently (and it turns out a
little less) buggy. Welcome to software.
next prev parent reply other threads:[~2001-05-30 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29 4:10 ` Jakob Østergaard
2001-05-29 4:26 ` safemode
2001-05-29 4:38 ` Jeff Garzik
2001-05-29 6:04 ` Mike Galbraith
2001-05-29 14:06 ` Gerhard Mack
2001-05-29 4:46 ` G. Hugh Song
2001-05-29 4:57 ` Jakob Østergaard
2001-05-29 7:13 ` Marcelo Tosatti
2001-05-29 9:10 ` Alan Cox
2001-05-29 15:37 ` elko
2001-05-29 20:09 ` Plain 2.4.5 VM... (and 2.4.5-ac3) Vincent Stemen
2001-05-29 20:16 ` Alan Cox
2001-05-29 21:36 ` Vincent Stemen
2001-05-30 6:02 ` Mike Galbraith
2001-05-30 19:58 ` Vincent Stemen
2001-05-30 20:11 ` Alan Cox [this message]
2001-05-30 20:17 ` Mike Galbraith
2001-05-31 3:47 ` Vincent Stemen
2001-05-31 6:18 ` Mike Galbraith
2001-05-30 20:30 ` Rik van Riel
2001-05-31 3:11 ` Vincent Stemen
2001-05-30 21:59 ` Vincent Stemen
2001-05-30 20:16 ` Rik van Riel
2001-05-31 17:23 Benjamin Redelings I
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=E155CJM-0006XT-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxkernel@AdvancedResearch.org \
--cc=mikeg@wen-online.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®