From: Dieter Nützel <Dieter.Nuetzel@hamburg.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Grover <andrew.grover@intel.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
"Linux ACPI List" <acpi@phobos.fachschaften.tu-muenchen.de>
Subject: Re: Linux-2.4.1-pre11
Date: Mon, 29 Jan 2001 03:20:36 +0100 [thread overview]
Message-ID: <01012903203600.00304@SunWave1> (raw)
In-Reply-To: <Pine.LNX.4.10.10101281346030.4151-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101281346030.4151-100000@penguin.transmeta.com>
Am Sonntag, 28. Januar 2001 22:46 schrieb Linus Torvalds:
> On Sun, 28 Jan 2001, Dieter Nützel wrote:
> > > I just uploaded it to kernel.org, and I expect that I'll do the final
> > > 2.4.1 tomorrow, before leaving for NY and LinuxWorld. Please test that
> > > the pre-kernel works for you..
> >
> > Hello Linus,
> >
> > can we please see Andrew's latest ACPI fixes ([Acpi] ACPI source release
> > updated: 1-25-2001) in 2.4.1 final?
>
> Does it fix stuff? Andrew?
I am the loser :-(
2.4.1-pre10 (with Andrew's ACPI fixes included) and
2.4.1-pre11 + 1-25-2001 patch bring back the pppd slowdown on my system.
2.4.1-pre9 was fine...
AMD K7
MSI MS-6167 Rev. 1.0B (Irongate C4)
-Dieter
-
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:[~2001-01-29 2:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 19:23 Linux-2.4.1-pre11 Dieter Nützel
2001-01-28 21:46 ` Linux-2.4.1-pre11 Linus Torvalds
2001-01-28 21:52 ` Linux-2.4.1-pre11 Jeff Garzik
2001-01-28 22:53 ` Linux-2.4.1-pre11 Drew Bertola
2001-01-28 23:39 ` Linux-2.4.1-pre11 Drew Bertola
2001-01-29 0:09 ` Linux-2.4.1-pre11 Drew Bertola
2001-01-29 3:48 ` Linux-2.4.1-pre11 Jeff Garzik
2001-01-28 22:08 ` Linux-2.4.1-pre11 Derek Wildstar
2001-01-29 2:20 ` Dieter Nützel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 18:07 Linux-2.4.1-pre11 Grover, Andrew
[not found] <Pine.LNX.4.31.0101281845420.6761-100000@argo.starforce.com>
2001-01-29 1:22 ` Linux-2.4.1-pre11 Derek Wildstar
2001-01-28 23:55 linux-2.4.1-pre11 Louis Garcia
2001-01-28 22:37 ` linux-2.4.1-pre11 Arnaldo Carvalho de Melo
2001-01-29 2:17 ` linux-2.4.1-pre11 Louis Garcia
2001-01-28 18:31 Linux-2.4.1-pre11 Linus Torvalds
2001-01-29 0:55 ` Linux-2.4.1-pre11 David D.W. Downey
2001-01-29 0:59 ` Linux-2.4.1-pre11 Michael H. Warfield
2001-01-29 1:03 ` Linux-2.4.1-pre11 David D.W. Downey
2001-01-29 1:17 ` Linux-2.4.1-pre11 Bob Chiodini
2001-01-29 1:10 ` Linux-2.4.1-pre11 David D.W. Downey
2001-01-29 1:10 ` Linux-2.4.1-pre11 Michael H. Warfield
2001-01-28 23:59 ` Linux-2.4.1-pre11 Arnaldo Carvalho de Melo
2001-01-29 2:36 ` Linux-2.4.1-pre11 Linus Torvalds
2001-01-29 1:10 ` Linux-2.4.1-pre11 Luc de Louw
2001-01-29 10:02 ` Linux-2.4.1-pre11 Meelis Roos
2001-01-29 10:26 ` Linux-2.4.1-pre11 Harold Oga
2001-01-29 10:55 ` Linux-2.4.1-pre11 Ondrej Sury
2001-01-29 23:33 ` Linux-2.4.1-pre11 Harold Oga
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=01012903203600.00304@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=andrew.grover@intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox