From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@vger.kernel.org
Cc: Thomas Renninger <trenn@suse.de>,
cpufreq@vger.kernel.org, linux@dominikbrodowski.net
Subject: Re: [PATCH 8/8] patch cpupower_ivy_bridge_support.patch
Date: Mon, 26 Nov 2012 21:49:20 +0100 [thread overview]
Message-ID: <2861427.bmEteVGXpd@vostro.rjw.lan> (raw)
In-Reply-To: <201211261646.16882.trenn@suse.de>
On Monday, November 26, 2012 04:46:16 PM Thomas Renninger wrote:
> On Saturday, November 24, 2012 10:49:52 AM Rafael J. Wysocki wrote:
> > Please add (1) a useful subject, (2) a changelog and (3) a sign-off tag.
> Sure, sorry about that.
> But be careful, this one is wrong:
>
> > > + case 0x2D: /* SNB Xeon */
> > > + case 0x3A: /* IVB */
> > > + case 0x3D: /* IVB Xeon */
> It's family 0x3E
> a copy and paste bug that has been taken over from
> turbostat, there it already got adjusted from 0x3D to 0x3E.
>
> I resend the whole series today or tomorrow.
OK
Should I drop the current one for now?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
parent reply other threads:[~2012-11-26 20:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201211261646.16882.trenn@suse.de>]
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=2861427.bmEteVGXpd@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=trenn@suse.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