From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Jones <davej@redhat.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.de>,
cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: my dothan didn't work with cpufreq...
Date: Mon, 02 Aug 2004 13:17:53 -0700 [thread overview]
Message-ID: <1091477873.18905.1.camel@localhost> (raw)
In-Reply-To: <20040802192608.GA17023@redhat.com>
On Mon, 2004-08-02 at 20:26 +0100, Dave Jones wrote:
> I merged this, but something occurred to me whilst eyeballing
> the diffs. Rather than duplicating X86_VENDOR_INTEL in every
> entry of the struct, how about we check it in one place?
>
> I'm unaware of any vendor planning to duplicate speedstep,
> but even if AMD/VIA threw away their current implementations
> in favour of a bit-for-bit compatible implementation, it
> wouldn't be hard to add an extra if()
I had the same thought. I already added the vendor check at the top of
the init function, so in theory nothing else should need to look at it.
So, we can just drop the vendor entries in those tables without having
to do anything else.
J
next prev parent reply other threads:[~2004-08-02 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 20:54 my dothan didn't work with cpufreq Damien Marchal
2004-07-13 9:49 ` Dominik Brodowski
2004-07-14 10:50 ` Damien Marchal
2004-07-16 8:19 ` Dominik Brodowski
2004-07-22 1:55 ` Jeremy Fitzhardinge
2004-07-22 6:04 ` Dominik Brodowski
2004-07-22 6:56 ` Jeremy Fitzhardinge
2004-07-22 9:31 ` Dominik Brodowski
2004-07-22 17:34 ` Jeremy Fitzhardinge
2004-07-23 19:38 ` Dominik Brodowski
2004-07-24 1:27 ` Jeremy Fitzhardinge
2004-07-24 7:06 ` Dominik Brodowski
2004-08-02 19:26 ` Dave Jones
2004-08-02 20:17 ` Jeremy Fitzhardinge [this message]
2004-08-02 20:29 ` Dave Jones
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=1091477873.18905.1.camel@localhost \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.