From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH] powercap/intel_rapl: Add support for Kabylake
Date: Mon, 25 Apr 2016 08:36:47 -0700 [thread overview]
Message-ID: <20160425083647.08bf483a@icelake> (raw)
In-Reply-To: <CAJZ5v0imwM3RCPM8QTWSWwEOfyCUZUTECMEa1hQOhyCLW06K_g@mail.gmail.com>
On Mon, 25 Apr 2016 16:20:17 +0200
"Rafael J. Wysocki" <rafael@kernel.org> wrote:
> How urgent is this?
>
> Can we live without it in 4.6 in particular?
not urgent.
next prev parent reply other threads:[~2016-04-25 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 17:17 [PATCH] powercap/intel_rapl: Add support for Kabylake Jacob Pan
2016-04-25 14:20 ` Rafael J. Wysocki
2016-04-25 15:36 ` Jacob Pan [this message]
2016-04-27 21:34 ` 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=20160425083647.08bf483a@icelake \
--to=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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