From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dominik Brodowski <linux@brodo.de>
Cc: acpi-devel@lists.sourceforge.net,
Ducrot Bruno <ducrot@poupinou.org>,
Andrew Grover <andrew.grover@intel.com>,
cpufreq list <cpufreq@www.linux.org.uk>,
David Moore <dcm@acm.org>,
"Adachi, Kenichi" <adachi@rd.scei.sony.co.jp>
Subject: Re: [RFC] cpufreq: use new acpi processor perflib in speedstep-centrino [Was: Re: [ACPI] _PDC method in DSDT]
Date: Fri, 05 Sep 2003 09:53:32 -0700 [thread overview]
Message-ID: <1062780812.23453.40.camel@localhost.localdomain> (raw)
In-Reply-To: <20030904231932.GA8518@brodo.de>
On Thu, 2003-09-04 at 16:19, Dominik Brodowski wrote:
> This patch modifies the speedstep-centrino driver to use the ACPI
> processor perflib if no hardcoded value could be found. Centrino-specific
> stuff is taken from a patch to arch/i386/kernel/cpu/cpufreq/acpi.c by
> David Moore [in this thread].
Sorry, I haven't really been following this thread. What's the complete
minimal set of other patches I need to make this one work? Are they
against 2.5.0-test4?
Thanks,
J
prev parent reply other threads:[~2003-09-05 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 9:19 [ACPI] _PDC method in DSDT Grover, Andrew
2003-06-23 13:38 ` Dominik Brodowski
2003-06-23 16:11 ` Ducrot Bruno
2003-06-23 17:12 ` Jeremy Fitzhardinge
2003-06-23 20:02 ` David Moore
2003-06-23 21:37 ` Dominik Brodowski
2003-06-24 1:14 ` David Moore
2003-06-24 1:37 ` Jeremy Fitzhardinge
2003-06-24 2:02 ` David Moore
2003-06-24 2:16 ` Jeremy Fitzhardinge
2003-06-24 9:18 ` Ducrot Bruno
2003-06-24 21:47 ` David Moore
2003-06-26 10:40 ` Ducrot Bruno
2003-06-26 11:13 ` Ducrot Bruno
2003-09-04 23:19 ` [RFC] cpufreq: use new acpi processor perflib in speedstep-centrino [Was: Re: [ACPI] _PDC method in DSDT] Dominik Brodowski
2003-09-05 16:53 ` Jeremy Fitzhardinge [this message]
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=1062780812.23453.40.camel@localhost.localdomain \
--to=jeremy@goop.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=adachi@rd.scei.sony.co.jp \
--cc=andrew.grover@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=dcm@acm.org \
--cc=ducrot@poupinou.org \
--cc=linux@brodo.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