From: "Luc, Piotr" <Piotr.Luc@intel.com>
To: "Brown, Len" <len.brown@intel.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [PATCH 0/2]tools/power turbostat: enable turbostat to support Knights Mill (KNM)
Date: Mon, 24 Oct 2016 16:07:23 +0000 [thread overview]
Message-ID: <1477324929.3927.23.camel@intel.com> (raw)
In-Reply-To: <20161018210652.29365-1-piotr.luc@intel.com>
On Tue, 2016-10-18 at 23:06 +0200, Piotr Luc wrote:
> This patchset is rebased onto
> 08328814256d888634ff15ba8fb67e2ae4340b64.
>
> First patch improves code style by replacing raw numbers
> of CPUID with descriptive macros of processor names.
>
> The second patch adds Knights Mill (KNM) to the list of CPUIDs
> supported
> by turbostat.
>
> Both patches come in new versions where trailing comments, which
> described CPUs, are removed because self-descriptive macros are
> used instead raw numbers.
>
> Piotr Luc (2):
> tools/power turbostat: Use Intel family processor macros
> tools/power turbostat: enable turbostat to support Knights Mill
> (KNM)
>
> tools/power/x86/turbostat/Makefile | 3 +-
> tools/power/x86/turbostat/turbostat.c | 250 ++++++++++++++++++----
> ------------
> 2 files changed, 131 insertions(+), 122 deletions(-)
>
Hi
I wonder if you could share with me what I need to do more to make the
patchset be accepted?
Regards,
Piotr
next prev parent reply other threads:[~2016-10-24 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 21:06 Piotr Luc
2016-10-18 21:06 ` [PATCH v3 1/2] tools/power turbostat: Use Intel family processor macros Piotr Luc
2016-10-18 21:06 ` [PATCH v2 2/2] tools/power turbostat: enable turbostat to support Knights Mill (KNM) Piotr Luc
2016-10-24 16:07 ` Luc, Piotr [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-12 18:29 [PATCH 0/2] " Piotr Luc
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=1477324929.3927.23.camel@intel.com \
--to=piotr.luc@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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
Powered by JetHome