[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B1AF41572@HASMSX106.ger.corp.intel.com>
Date: Sun, 12 Jan 2014 09:00:16 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "arnd@...db.de" <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@...el.com>
Subject: RE: [char-misc 1/4] mei: do not run reset flow from the interrupt
thread
> 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?
Reported here:
https://lkml.org/lkml/2013/12/22/102
https://lkml.org/lkml/2013/11/1/190
https://bugzilla.novell.com/show_bug.cgi?id=821619
maybe few more other places, I've already tried to address the issue but it looks I didn't hit the nail till now..
> Is there a work-around without this patchset?
Disabling timer_work has same effect
https://lkml.org/lkml/2013/11/7/179
but I haven't checked fi it does have another side effects mostly in AMTHI.
>
> As it is, I can't take something this big for the stable tree, sorry.
>
Understood, I will try to find smaller fix to target stable.
Thanks
Tomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists