From: Luis Henriques <luis.henriques@canonical.com>
To: William Dauchy <william@gandi.net>
Cc: "David E. Box" <david.e.box@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"Ingo Molnar" <mingo@kernel.org>,
"“stable@vger.kernel.org”" <stable@vger.kernel.org>
Subject: Re: stable fix for IOSF in Kconfig
Date: Thu, 9 Jul 2015 14:42:52 +0100 [thread overview]
Message-ID: <20150709134252.GD2190@ares> (raw)
In-Reply-To: <20150520122747.GA7410@gandi.net>
On Wed, May 20, 2015 at 02:27:47PM +0200, William Dauchy wrote:
> Hello,
>
> Using a stable 3.14.x kernel, I had an issue where I was unable to set
> IOSF_MBI as builtin.
>
> I applied the following commit on top of my 3.14.x:
>
> commit aa8e4f22ab7773352ba3895597189b8097f2c307
> Author: David E. Box <david.e.box@linux.intel.com>
> Date: Wed Aug 27 14:40:39 2014 -0700
> x86/iosf: Add Kconfig prompt for IOSF_MBI selection
>
Thanks, I'm queuing this commit for the 3.16 kernel as well.
Cheers,
--
Lu�s
> This fixes my issue.
> Do you think it's a good candidate for stable branches?
>
>
> we may also consider the following commit for stable:
> commit ced3ce760b8df08e8bafba44f6b40407df2d0402
> Author: David E. Box <david.e.box@linux.intel.com>
> Date: Wed Sep 17 22:13:50 2014 -0700
> x86/platform/intel/iosf: Add better description of IOSF driver in config
>
>
> Regards,
> --
> William
prev parent reply other threads:[~2015-07-09 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 12:27 stable fix for IOSF in Kconfig William Dauchy
2015-05-20 15:59 ` Greg KH
2015-05-20 16:04 ` William Dauchy
2015-06-29 22:53 ` Greg KH
2015-07-02 9:24 ` William Dauchy
2015-07-02 13:07 ` Greg KH
2015-07-02 13:19 ` William Dauchy
2015-07-08 7:28 ` Greg KH
2015-07-09 13:42 ` 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=20150709134252.GD2190@ares \
--to=luis.henriques@canonical.com \
--cc=david.e.box@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=william@gandi.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).