[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1405130020050.6261@ionos.tec.linutronix.de>
Date: Tue, 13 May 2014 00:37:21 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>
cc: LKML <linux-kernel@...r.kernel.org>, Dave Jones <davej@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Darren Hart <darren@...art.com>,
Davidlohr Bueso <davidlohr@...com>,
Ingo Molnar <mingo@...nel.org>,
Clark Williams <williams@...hat.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
Roland McGrath <roland@...k.frob.com>,
Carlos ODonell <carlos@...hat.com>,
Jakub Jelinek <jakub@...hat.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [patch 0/3] futex/rtmutex: Fix issues exposed by trinity
On Mon, 12 May 2014, Steven Rostedt wrote:
> I did admit I made a mistake. If you read the rest of my email that you
> cut off, I said "Sure, I should have pushed Lai for that at the time.
> Lessons learned. I was expecting he would do so after we got to a final
> version of the patch but I was also working on other things at the time
> and forgot to remind him."
>
> I even stated that I'm doing better now. That means I have learned from
> my mistakes. And continue to do so.
Sure, with your latest multi reader patches you break even the compile
with CONFIG_DEBUG_RT_MUTEXES=y due to:
+ debug_rt_mutex_print_deadlock(waiter);
I'm really impressed by your improvements.
Thanks,
tglx
--
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