From: Jean Delvare <khali@linux-fr.org>
To: "Yu, Fenghua" <fenghua.yu@intel.com>, Andi Kleen <andi@firstfloor.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>,
Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2
Date: Thu, 26 May 2011 09:49:05 +0200 [thread overview]
Message-ID: <20110526094905.536ca3f1@endymion.delvare> (raw)
In-Reply-To: <493994B35A117E4F832F97C4719C4C04011E2157D6@orsmsx505.amr.corp.intel.com>
On Wed, 25 May 2011 19:08:27 -0700, Yu, Fenghua wrote:
> > -----Original Message-----
> > From: Jean Delvare [mailto:khali@linux-fr.org]
> > Sent: Wednesday, May 25, 2011 1:54 PM
> > To: Andi Kleen
> > Cc: x86@kernel.org; linux-kernel@vger.kernel.org; Andi Kleen;
> > jbeulich@novell.com; Yu, Fenghua
> > Subject: Re: [PATCH 3/3] coretemp: Get microcode revision from cpu_data
> > v2
> >
> > Hi Andi,
> >
> > On Wed, 25 May 2011 12:32:28 -0700, Andi Kleen wrote:
> > > From: Andi Kleen <ak@linux.intel.com>
> > >
> > > Now that the ucode revision is available in cpu_data remove
> > > the existing code in coretemp.c to query it manually. Read the ucode
> > > revision from cpu_data instead
> >
> > Where is this available? Not upstream yet, apparently. I get a build
> > failure here.
> >
>
> This is one of three patches. Cpu_data is defined in the first patch. You need to get the other two to test them.
OK, thanks. This is (build-)tested now.
Acked-by: Jean Delvare <khali@linux-fr.org>
Andi, do you plan to merge this in 2.6.40 or later?
--
Jean Delvare
next prev parent reply other threads:[~2011-05-26 7:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 19:32 [PATCH 1/3] x86, intel: Output microcode revision v2 Andi Kleen
2011-05-25 19:32 ` [PATCH 2/3] x86, intel: Use cpu_update for Atom errata check Andi Kleen
2011-05-26 7:39 ` Jean Delvare
2011-05-25 19:32 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
2011-05-25 20:53 ` Jean Delvare
2011-05-26 2:08 ` Yu, Fenghua
2011-05-26 7:49 ` Jean Delvare [this message]
2011-05-25 19:52 ` [PATCH 1/3] x86, intel: Output microcode revision v2 Ingo Molnar
2011-05-25 20:06 ` Andi Kleen
2011-05-25 21:40 ` Thomas Gleixner
2011-05-25 23:58 ` Andy Lutomirski
2011-05-26 7:33 ` Jean Delvare
2011-07-01 19:21 [PATCH 1/3] x86, intel: Output microcode revision v3 Andi Kleen
2011-07-01 19:21 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
2011-07-06 23:57 [PATCH 1/3] x86, intel: Output microcode revision v3 Andi Kleen
2011-07-06 23:57 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
2011-07-11 11:46 ` Jean Delvare
2011-08-29 23:47 [PATCH 1/3] x86, intel: Output microcode revision v4 Andi Kleen
2011-08-29 23:47 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
2011-09-28 23:19 [PATCH 1/3] x86, intel: Output microcode revision v5 Andi Kleen
2011-09-28 23:19 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
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=20110526094905.536ca3f1@endymion.delvare \
--to=khali@linux-fr.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=fenghua.yu@intel.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).