From: Greg KH <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: Re: [char-misc 1/4] mei: do not run reset flow from the interrupt thread
Date: Sat, 11 Jan 2014 15:38:48 -0800 [thread overview]
Message-ID: <20140111233848.GB6819@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B1AF40FBF@HASMSX106.ger.corp.intel.com>
On Sat, Jan 11, 2014 at 10:46:14PM +0000, Winkler, Tomas wrote:
>
>
> >
> > This is a _really_ big patch for a stable kernel tree. Are you sure
> > it's needed there? Please go read Documentation/stable_kernel_rules.txt
> > again.
>
> I understand it's big though currently I do not have significantly
> simpler fix for the issue, all 4 patches are needed to make the reset
> issue go away.
What is the "reset issue"? Who is it affecting? What is the problem?
Is there a work-around without this patchset?
As it is, I can't take something this big for the stable tree, sorry.
greg k-h
next prev parent reply other threads:[~2014-01-11 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:19 [char-misc 0/4] mei: reset fix Tomas Winkler
2014-01-08 18:19 ` [char-misc 1/4] mei: do not run reset flow from the interrupt thread Tomas Winkler
2014-01-08 23:24 ` Greg KH
2014-01-11 22:46 ` Winkler, Tomas
2014-01-11 23:38 ` Greg KH [this message]
2014-01-12 9:00 ` Winkler, Tomas
2014-01-08 18:19 ` [char-misc 2/4] mei: use hbm idle state to prevent spurious resets Tomas Winkler
2014-01-08 18:19 ` [char-misc 3/4] mei: revamp mei reset state machine Tomas Winkler
2014-01-08 23:24 ` Greg KH
2014-01-08 23:26 ` Greg KH
2014-01-11 16:25 ` Winkler, Tomas
2014-01-08 18:19 ` [char-misc 4/4] mei: limit the number of consecutive resets Tomas Winkler
2014-01-08 23:27 ` Greg KH
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=20140111233848.GB6819@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--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.