linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luc, Piotr" <Piotr.Luc@intel.com>
To: "lenb@kernel.org" <lenb@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [RESEND,04/11] x86/intel_idle: Add Knights Mill CPUID
Date: Tue, 25 Oct 2016 10:36:29 +0000	[thread overview]
Message-ID: <1477391475.3927.36.camel@intel.com> (raw)
In-Reply-To: <20161013153105.2517-5-piotr.luc@intel.com>

Hi Len,

Could you tell me what more do I need to do to get the patchset
accepted?

The mentioned path 03/11 is already merged in 4.9.rc2.

Thanks,
Piotr

On Thu, 2016-10-13 at 17:30 +0200, Piotr Luc wrote:
> Add Knights Mill (KNM) to the list of CPUIDs supported by intel_idle.
> 
> Signed-off-by: Piotr Luc <piotr.luc@intel.com>
> Reviewed-by: Dave Hansen <dave.hansen@intel.com>
> Cc: linux-pm@vger.kernel.org
> Cc: Len Brown <lenb@kernel.org>
> Cc: linux-kernel@vger.kernel.org
> ---
> This patch depends on [PATCH 03/11] x86/cpu/intel: Add Knights Mill 
> to Intel family
> 
>  drivers/idle/intel_idle.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> index 67ec58f..69047a0 100644
> --- a/drivers/idle/intel_idle.c
> +++ b/drivers/idle/intel_idle.c
> @@ -1084,6 +1084,7 @@ static const struct x86_cpu_id intel_idle_ids[]
> __initconst = {
>  	ICPU(INTEL_FAM6_KABYLAKE_DESKTOP,	idle_cpu_skl),
>  	ICPU(INTEL_FAM6_SKYLAKE_X,		idle_cpu_skx),
>  	ICPU(INTEL_FAM6_XEON_PHI_KNL,		idle_cpu_knl),
> +	ICPU(INTEL_FAM6_XEON_PHI_KNM,		idle_cpu_knl),
>  	ICPU(INTEL_FAM6_ATOM_GOLDMONT,		idle_cpu_bxt),
>  	ICPU(INTEL_FAM6_ATOM_DENVERTON,		idle_cpu_dnv)
> ,
>  	{}

  reply	other threads:[~2016-10-25 10:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 15:30 [RESEND PATCH 00/11] Add Knights Mill CPU ID Piotr Luc
2016-10-13 15:30 ` [RESEND PATCH 01/11] EDAC, sb_edac: Use Intel family processor macros Piotr Luc
2016-10-13 22:01   ` Borislav Petkov
2016-10-13 15:30 ` [PATCH v2 02/11] tools/power turbostat: " Piotr Luc
2016-10-14 11:56   ` Thomas Gleixner
2016-10-24 13:15     ` Luc, Piotr
2016-10-13 15:30 ` [RESEND PATCH 03/11] x86/cpu/intel: Add Knights Mill to Intel family Piotr Luc
2016-10-13 15:30 ` [RESEND PATCH 04/11] x86/intel_idle: Add Knights Mill CPUID Piotr Luc
2016-10-25 10:36   ` Luc, Piotr [this message]
2016-12-01  5:29   ` Len Brown
2016-12-01  8:45     ` Luc, Piotr
2016-10-13 15:30 ` [RESEND PATCH 05/11] EDAC, sb_edac: " Piotr Luc
2016-10-13 22:04   ` Borislav Petkov
2016-10-19 10:38     ` Borislav Petkov
2016-10-13 15:31 ` [RESEND PATCH 06/11] cpufreq: intel_pstate: " Piotr Luc
2016-10-13 17:51   ` Srinivas Pandruvada
2016-10-25 10:48     ` Luc, Piotr
2016-10-25 11:16       ` Rafael J. Wysocki
2016-10-25 11:44         ` Luc, Piotr
2016-11-30 16:19           ` Luc, Piotr
2016-11-30 22:01             ` Rafael J. Wysocki
2016-11-30 22:16               ` Luc, Piotr
2016-10-13 15:31 ` [RESEND PATCH 07/11] perf/x86/intel: " Piotr Luc
2016-10-13 15:31 ` [RESEND PATCH 08/11] perf/x86/intel/rapl: " Piotr Luc
2016-10-13 15:31 ` [RESEND PATCH 09/11] perf/x86/intel/uncore: " Piotr Luc
2016-10-13 15:31 ` [RESEND PATCH 10/11] powercap / RAPL: " Piotr Luc
2016-10-25 10:41   ` [RESEND,10/11] " Luc, Piotr
2016-11-30 22:33     ` Luc, Piotr
2016-11-30 22:42       ` Rafael J. Wysocki
2016-10-13 15:31 ` [RESEND PATCH 11/11] tools/power turbostat: enable turbostat to support Knights Mill (KNM) Piotr Luc
2016-12-01  6:47   ` Len Brown
2016-12-01 11:17     ` Luc, Piotr
2016-10-13 21:56 ` [RESEND PATCH 00/11] Add Knights Mill CPU ID Rafael J. Wysocki
2016-10-24 16:13   ` Luc, Piotr

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=1477391475.3927.36.camel@intel.com \
    --to=piotr.luc@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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).