From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Nikhil Rao <nikhil.rao@intel.com>
Cc: Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powercap / RAPL: Support Knights Landing
Date: Tue, 19 May 2015 17:10:05 -0700 [thread overview]
Message-ID: <20150519171005.1f32c052@jacob-VirtualBox> (raw)
In-Reply-To: <4265007.tICN7CeGKt@vostro.rjw.lan>
On Wed, 20 May 2015 01:31:54 +0200
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> On Tuesday, May 19, 2015 03:37:49 PM Dasaratharaman Chandramouli
> wrote:
> > This patch enables intel_rapl driver to run on the
> > next-generation Intel(R) Xeon Phi Microarchitecture
> > code named "Knights Landing"
> >
> > Signed-off-by: Dasaratharaman Chandramouli
> > <dasaratharaman.chandramouli@intel.com>
>
> Jacob?
looks good.
Acked-by:Jacob Pan <jacob.jun.pan@linux.intel.com>
>
> > ---
> > drivers/powercap/intel_rapl.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/powercap/intel_rapl.c
> > b/drivers/powercap/intel_rapl.c index fd24323..5796332 100644
> > --- a/drivers/powercap/intel_rapl.c
> > +++ b/drivers/powercap/intel_rapl.c
> > @@ -1069,6 +1069,7 @@ static const struct x86_cpu_id rapl_ids[]
> > __initconst = { RAPL_CPU(0x4A, rapl_defaults_atom),/* Tangier */
> > RAPL_CPU(0x56, rapl_defaults_core),/* Future Xeon */
> > RAPL_CPU(0x5A, rapl_defaults_atom),/* Annidale */
> > + RAPL_CPU(0x57, rapl_defaults_hsw_server),/* Knights
> > Landing */ {}
> > };
> > MODULE_DEVICE_TABLE(x86cpu, rapl_ids);
> >
>
[Jacob Pan]
next prev parent reply other threads:[~2015-05-20 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 22:37 [PATCH] powercap / RAPL: Support Knights Landing Dasaratharaman Chandramouli
2015-05-19 23:31 ` Rafael J. Wysocki
2015-05-20 0:10 ` Jacob Pan [this message]
2015-05-21 1:01 ` Rafael J. Wysocki
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=20150519171005.1f32c052@jacob-VirtualBox \
--to=jacob.jun.pan@linux.intel.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/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).