From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH] powercap/intel_rapl: Add support for Gemini Lake
Date: Mon, 24 Apr 2017 09:54:12 -0700 [thread overview]
Message-ID: <20170424095412.5fda5fc6@jacob-builder> (raw)
In-Reply-To: <20170423141520.7517-1-david.e.box@linux.intel.com>
On Sun, 23 Apr 2017 07:15:20 -0700
"David E. Box" <david.e.box@linux.intel.com> wrote:
> From: "Box, David E" <david.e.box@intel.com>
>
> Gemini Lake RAPL support is similar to Goldmont.
>
Acked-by: Pan, Jacob jun <jacob.jun.pan@intel.com>
> Signed-off-by: David E. Box <david.e.box@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 9a25110..9ddad08 100644
> --- a/drivers/powercap/intel_rapl.c
> +++ b/drivers/powercap/intel_rapl.c
> @@ -1164,6 +1164,7 @@ static const struct x86_cpu_id rapl_ids[]
> __initconst = { RAPL_CPU(INTEL_FAM6_ATOM_MERRIFIELD,
> rapl_defaults_tng), RAPL_CPU(INTEL_FAM6_ATOM_MOOREFIELD,
> rapl_defaults_ann), RAPL_CPU(INTEL_FAM6_ATOM_GOLDMONT,
> rapl_defaults_core),
> + RAPL_CPU(INTEL_FAM6_ATOM_GEMINI_LAKE,
> rapl_defaults_core), RAPL_CPU(INTEL_FAM6_ATOM_DENVERTON,
> rapl_defaults_core),
> RAPL_CPU(INTEL_FAM6_XEON_PHI_KNL,
> rapl_defaults_hsw_server),
[Jacob Pan]
prev parent reply other threads:[~2017-04-24 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 14:15 [PATCH] powercap/intel_rapl: Add support for Gemini Lake David E. Box
2017-04-24 16:54 ` Jacob Pan [this message]
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=20170424095412.5fda5fc6@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).