From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: davej@redhat.com, cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: [PATCH 1/4] speedstep-centrino: move to per-CPU analyzing of CPUs
Date: Fri, 20 Feb 2004 15:37:57 -0800 [thread overview]
Message-ID: <1077320156.4205.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20040220084424.GA10473@dominikbrodowski.de>
On Fri, 2004-02-20 at 00:44, Dominik Brodowski wrote:
> Move the table matching into an own function; only the FEATURE_EST bit is checked
> in module_init() directly. As cpufreq drivers aren't sticky any longer (see other
> pending patch sent to cpufreq mailing list a few minutes ago), this will not
> change user-visible behaviour.
These all look reasonable to me. I tried testing the ACPI table change,
but it isn't obvious about where it gets its frequency table from - it
might be nice to add a hint to the banner.
J
prev parent reply other threads:[~2004-02-20 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 8:44 [PATCH 1/4] speedstep-centrino: move to per-CPU analyzing of CPUs Dominik Brodowski
2004-02-20 23:37 ` 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=1077320156.4205.1.camel@localhost.localdomain \
--to=jeremy@goop.org \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux@dominikbrodowski.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