From: Ben Pfaff <blp@cs.stanford.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [Ubuntu PATCH] acpi: Add IBM R60E laptop to proc-idle blacklist
Date: Mon, 19 Jun 2006 20:51:09 -0700 [thread overview]
Message-ID: <87lkrstrgy.fsf@benpfaff.org> (raw)
In-Reply-To: 20060619203333.5e897ead.akpm@osdl.org
Andrew Morton <akpm@osdl.org> writes:
> On Thu, 15 Jun 2006 13:00:43 -0700
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
>> [UBUNTU:acpi] Add IBM R60E laptop to proc-idle blacklist.
>> + { set_max_cstate, "IBM ThinkPad R40e", {
>> + DMI_MATCH(DMI_BIOS_VENDOR, "IBM"),
>> + DMI_MATCH(DMI_BIOS_VERSION, "1SET70WW") }, (void*)1},
>
> It seems that every R40e in the world is in that table.
The email says R60e.
The string says R40e.
Which is correct?
--
Ben Pfaff
email: blp@cs.stanford.edu
web: http://benpfaff.org
next prev parent reply other threads:[~2006-06-20 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 20:00 [Ubuntu PATCH] acpi: Add IBM R60E laptop to proc-idle blacklist Randy Dunlap
2006-06-20 3:33 ` Andrew Morton
2006-06-20 3:51 ` Ben Pfaff [this message]
2006-06-20 5:16 ` Randy.Dunlap
2006-06-20 9:30 ` Matthew Garrett
2006-06-20 9:30 ` Matthew Garrett
2006-06-20 19:56 ` Randy Dunlap
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=87lkrstrgy.fsf@benpfaff.org \
--to=blp@cs.stanford.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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