From: Len Brown <lenb@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: trenn@suse.de, Andi Kleen <andi@firstfloor.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Knut Petersen <Knut_Petersen@t-online.de>,
linux-kernel@vger.kernel.org, mjg59@srcf.ucam.org
Subject: Re: 2.6.22 regression: thermal trip points
Date: Tue, 7 Aug 2007 14:58:45 -0400 [thread overview]
Message-ID: <200708071458.45687.lenb@kernel.org> (raw)
In-Reply-To: <20070806095504.GA1934@elf.ucw.cz>
On Monday 06 August 2007 05:55, Pavel Machek wrote:
> > For the
> > upstream kernel, I think it is more appropriate to expose and fix
> > the fundamental problems. For distro kernels, I'm less concerned
> > if you hide bugs instead of fixing them.
>
> This is okay as long as you are willing to work around the fundamental
> problems in kernel. You are unable to _fix_ them. They are broken
> BIOSes.
The thing Linux needs to figure out is why Windows doesn't
get confused by what Linux claims to be broken BIOS.
So far I have one live sighting to be addressed by
the upstream kernel (from Knut). I'm certainly looking
forward to the 2nd live sighting...
-Len
next prev parent reply other threads:[~2007-08-07 18:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 8:40 2.6.22 regression: thermal trip points Knut Petersen
2007-08-02 8:52 ` Andrew Morton
2007-08-02 10:48 ` Andi Kleen
2007-08-02 11:00 ` Alan Cox
2007-08-02 12:05 ` Andi Kleen
2007-08-02 13:04 ` Alan Cox
2007-08-02 13:16 ` Andi Kleen
2007-08-02 15:57 ` Pavel Machek
2007-08-02 18:38 ` Andi Kleen
2007-08-02 18:40 ` Matthew Garrett
2007-08-03 11:16 ` Thomas Renninger
2007-08-03 18:59 ` Len Brown
2007-08-06 9:55 ` Pavel Machek
2007-08-07 18:58 ` Len Brown [this message]
2007-08-07 21:49 ` Pavel Machek
2007-08-13 12:30 ` Pavel Machek
2007-08-02 15:55 ` Pavel Machek
2007-08-02 9:42 ` Thomas Renninger
2007-08-02 9:45 ` Adrian Schröter
2007-08-02 9:58 ` Thomas Renninger
2007-08-02 11:02 ` Alan Cox
2007-08-02 11:13 ` Matthew Garrett
2007-08-02 11:45 ` Thomas Renninger
2007-08-02 11:56 ` Matthew Garrett
2007-08-02 12:42 ` Thomas Renninger
2007-08-02 12:55 ` Matthew Garrett
2007-08-02 11:59 ` Alan Cox
2007-08-02 11:57 ` Matthew Garrett
2007-08-02 12:06 ` Thomas Renninger
2007-08-02 12:15 ` Matthew Garrett
2007-08-02 12:35 ` Thomas Renninger
2007-08-02 12:47 ` Matthew Garrett
2007-08-02 21:56 ` Len Brown
2007-08-02 11:32 ` Knut Petersen
2007-08-02 12:06 ` Andi Kleen
2007-08-02 13:06 ` Alan Cox
2007-08-02 16:07 ` Pavel Machek
2007-08-02 19:25 ` Krzysztof Halasa
2007-08-02 21:56 ` Len Brown
2007-08-03 11:43 ` Renato S. Yamane
2007-08-03 18:35 ` Len Brown
2007-08-03 12:53 ` Knut Petersen
2007-08-03 18:30 ` Len Brown
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=200708071458.45687.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=Knut_Petersen@t-online.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
--cc=trenn@suse.de \
/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