Re: [patch 0/4] 3.12-stable rtmutex @stable backports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 10 Jul 2014, Steven Rostedt wrote:

> On Thu, 10 Jul 2014 19:40:21 +0200
> Mike Galbraith <umgwanakikbuti@xxxxxxxxx> wrote:
> 
> > On Thu, 2014-07-10 at 09:16 -0700, Greg Kroah-Hartman wrote: 
> > > On Thu, Jul 10, 2014 at 08:12:18AM +0200, Mike Galbraith wrote:
> > > > On Mon, 2014-07-07 at 16:55 +0200, Mike Galbraith wrote: 
> > > > > Seems the below stable tagged rtmutex fixes won't go further back than
> > > > > 3.14 unless someone does the leg work of making them applicable.
> > > > > 
> > > > > Ergo, this series contains..
> > > > > 
> > > > > 397335f0 rtmutex: Fix deadlock detector for real
> > > > > 82084984 rtmutex: Detect changes in the pi lock chain
> > > > > 3d5c9340 rtmutex: Handle deadlock detection smarter
> > > > > 27e35715 rtmutex: Plug slow unlock race
> > > > 
> > > > Hohum, so much for a bunch of perfectly good kilowatthours.  (flush)
> > > 
> > > Well, I thought you wanted tglx to ack them, so I was waiting for that.
> > 
> > I did, but he's either too busy or grumpy to reply, so I figured !ACK of
> > his patches is equivalent to a NAK.  If they fly fine, if they don't,
> > that's fine too, he or someone else can do the leg work some other time
> > (or not) as they see fit.
> 
> He's too busy. A !ACK does not equate to a NAK. You know Thomas as well
> as I do. He enjoys making poetry with his NAKs ;-)

It was on my list for today :)

Acked-by-me
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]