From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dave Jones <davej@redhat•com>
Cc: linux-next@vger•kernel.org,
Matthias-Christian Ott <ott@mirix•org>,
Dominik Brodowski <linux@brodo•de>
Subject: Re: linux-next: cpufreq tree build failure
Date: Wed, 25 Feb 2009 15:23:40 +1100 [thread overview]
Message-ID: <20090225152340.6945b58c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090225034504.GA25446@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
Hi Dave,
On Tue, 24 Feb 2009 22:45:04 -0500 Dave Jones <davej@redhat•com> wrote:
>
> There were a bunch of 64bit Xeons made that lacked P-states.
> Though using p4-clockmod as a replacement isn't a good idea, but we should
> still allow it for thermal protection.
> Also some of the Atoms are 64bit capable, but also lack P-states.
>
> I'll nix the ifdefs and regenerate the tree.
OK, thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-25 4:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 6:21 linux-next: cpufreq tree build failure Stephen Rothwell
2009-02-24 16:51 ` Dave Jones
2009-02-25 3:29 ` Stephen Rothwell
2009-02-25 3:45 ` Dave Jones
2009-02-25 4:23 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-03 2:28 Stephen Rothwell
2009-08-03 23:22 ` Thomas Renninger
2009-08-03 23:44 ` Dave Jones
2009-02-05 7:54 Stephen Rothwell
2009-02-05 9:33 ` Thomas Renninger
2009-02-05 9:47 ` Thomas Renninger
2009-02-05 17:45 ` Dave Jones
2009-02-05 20:57 ` Thomas Renninger
2009-02-05 21:34 ` Dave Jones
2009-01-20 2:50 Stephen Rothwell
2009-01-20 5:30 ` Dave Jones
2009-01-20 6:23 ` Stephen Rothwell
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=20090225152340.6945b58c.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davej@redhat$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@brodo$(echo .)de \
--cc=ott@mirix$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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