From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: Re: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware
Date: Wed, 30 Nov 2016 10:24:54 +0100 [thread overview]
Message-ID: <20161130092454.GC19640@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B54333E6E@hasmsx108.ger.corp.intel.com>
On Tue, Nov 29, 2016 at 09:41:41PM +0000, Winkler, Tomas wrote:
>
>
> >
> > On Tue, Nov 29, 2016 at 07:21:43PM +0000, Winkler, Tomas wrote:
> > > >
> > > > On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote:
> > > > > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream
> > > > >
> > > > > Sunrise Point PCH with SPS Firmware doesn't expose working MEI
> > > > > interface, we need to quirk it out.
> > > > > The SPS Firmware is identifiable only on the first PCI function of
> > > > > the device.
> > > > >
> > > > > Cc: <stable@vger.kernel.org> #4.4
> > > > > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > > > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > ---
> > > > > drivers/misc/mei/hw-me.c | 10 ++++++++--
> > > > > drivers/misc/mei/pci-me.c
> > > > > | 4 ++--
> > > > > 2 files changed, 10 insertions(+), 4 deletions(-)
> > > >
> > > > I don't understand what this is for, it's already in the 4.8-stable
> > > > tree. And there you said it only needed to go to 4.6 and newer, yet you are
> > saying 4.4 here?
> > > > What am I supposed to do?
> > > >
> > >
> > > It's needed 4.4, but the original patch does apply cleanly only from 4.6 up, so
> > this is the rebased version over 4.4. Since 4.4 is a long term kernel this is
> > important.
> > > I see from time to time broken patches in stable, mostly in 3.X series, so I
> > prefer to do the back port myself.
> >
> > Ok, but your [char-misc] in the subject confused me. Please make this a bit
> > more explicit next time.
>
> I see, it's automated in my scripts. Will [char-misc 4.4] or [stable 4.4] works for you?
It's not that automated as it is misspelled in this series :)
Anyway, stable would make more sense, char-misc 4.4 does not mean
anything...
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-30 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:44 [char-msic 1/3] mei: me: disable driver on SPT SPS firmware Tomas Winkler
2016-11-29 12:44 ` [char-msic 2/3] mei: me: fix place for kaby point device ids Tomas Winkler
2016-11-29 19:15 ` Greg Kroah-Hartman
2016-11-29 20:13 ` Winkler, Tomas
2016-11-29 20:24 ` Winkler, Tomas
2016-11-29 21:32 ` Greg Kroah-Hartman
2016-11-29 21:43 ` Winkler, Tomas
2016-11-30 9:26 ` Patch "mei: me: fix place for kaby point device ids." has been added to the 4.4-stable tree gregkh
2016-11-29 12:44 ` [char-msic 3/3] mei: fix return value on disconnection Tomas Winkler
2016-11-29 19:15 ` Greg Kroah-Hartman
2016-11-29 20:15 ` Winkler, Tomas
2016-11-29 20:16 ` Winkler, Tomas
2016-11-29 19:14 ` [char-msic 1/3] mei: me: disable driver on SPT SPS firmware Greg Kroah-Hartman
2016-11-29 19:21 ` Winkler, Tomas
2016-11-29 21:31 ` Greg Kroah-Hartman
2016-11-29 21:41 ` Winkler, Tomas
2016-11-30 9:24 ` Greg Kroah-Hartman [this message]
2016-11-30 9:40 ` Winkler, Tomas
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=20161130092454.GC19640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.winkler@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 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.