From: Luis Henriques <luis.henriques@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Kamal Mostafa <kamal.mostafa@canonical.com>,
stable@vger.kernel.org, srinivas.pandruvada@linux.intel.com,
dirk.j.brandewie@intel.com, rafael.j.wysocki@intel.com,
viresh.kumar@linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org,
Kernel Team <kernel-team@lists.ubuntu.com>
Subject: Re: [PATCH][3.11.y] intel_pstate: fix no_turbo
Date: Tue, 17 Dec 2013 11:36:03 +0000 [thread overview]
Message-ID: <20131217113603.GB5044@hercules> (raw)
In-Reply-To: <20131211103520.GA6127@hercules>
On Wed, Dec 11, 2013 at 10:35:20AM +0000, Luis Henriques wrote:
> On Tue, Dec 10, 2013 at 02:37:28PM -0500, Joseph Salisbury wrote:
> > Hello,
> >
> > Please consider including mainline commit
> > 1ccf7a1cdafadd02e33e8f3d74370685a0600ec6 in the next v3.11.y release.
> >
> > It was included in the mainline tree as of v3.12-rc4. It has been
> > tested and confirmed
> > to resolve http://bugs.launchpad.net/bugs/1254091 .
> >
> > commit 1ccf7a1cdafadd02e33e8f3d74370685a0600ec6
> > Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> > Date: Tue Oct 1 10:28:41 2013 -0700
> >
> > intel_pstate: fix no_turbo
> >
> > Other stable trees may also want to pick up this commit.
> >
> > Sincerely,
> > Joseph Salisbury
> >
>
> Thanks Joseph, I'm queuing this patch for the 3.11 kernel.
Just FYI, I'm also queuing:
09c87e2 intel_pstate: Fix type mismatch warning
to remove a compilation warning on some architectures.
Cheers,
--
Luis
prev parent reply other threads:[~2013-12-17 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 19:37 [PATCH][3.11.y] intel_pstate: fix no_turbo Joseph Salisbury
2013-12-11 10:35 ` Luis Henriques
2013-12-17 11:36 ` Luis Henriques [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=20131217113603.GB5044@hercules \
--to=luis.henriques@canonical.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.j.brandewie@intel.com \
--cc=joseph.salisbury@canonical.com \
--cc=kamal.mostafa@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.