From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Brad Mouring <bmouring@ni.com>
Subject: Re: [patch 2/2] rtmutex: Detect changes in the pi lock chain
Date: Sat, 7 Jun 2014 09:31:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1406070930490.25930@nanos> (raw)
In-Reply-To: <20140606104923.3020a352@gandalf.local.home>
On Fri, 6 Jun 2014, Steven Rostedt wrote:
> On Thu, 05 Jun 2014 15:28:33 -0000
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > /**
> > @@ -764,7 +802,7 @@ __rt_mutex_slowlock(struct rt_mutex *loc
> > }
> >
> > static void rt_mutex_handle_deadlock(int res, int detect_deadlock,
> > - struct rtmutex_waiter *w)
> > + struct rt_mutex_waiter *w)
> > {
> > /*
> > * If the result is not -EDEADLOCK or the caller requested
> >
>
> This needs to be folded in patch 1.
I know :) quilt refresh folded it automagically :)
next prev parent reply other threads:[~2014-06-07 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 15:28 [patch 0/2] rtmutex: Sanitze deadlock detection and chain walk Thomas Gleixner
2014-06-05 15:28 ` [patch 1/2] rtmutex: Handle deadlock detection smarter Thomas Gleixner
2014-06-06 1:14 ` Steven Rostedt
2014-06-06 5:41 ` Thomas Gleixner
2014-06-06 2:59 ` Steven Rostedt
2014-06-06 5:40 ` Thomas Gleixner
2014-06-09 16:49 ` [tip:locking/urgent] " tip-bot for Thomas Gleixner
2014-06-05 15:28 ` [patch 2/2] rtmutex: Detect changes in the pi lock chain Thomas Gleixner
2014-06-06 9:48 ` Peter Zijlstra
2014-06-06 9:58 ` Steven Rostedt
2014-06-06 14:25 ` Steven Rostedt
2014-06-06 14:49 ` Steven Rostedt
2014-06-07 7:31 ` Thomas Gleixner [this message]
2014-06-09 16:49 ` [tip:locking/urgent] " tip-bot for Thomas Gleixner
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=alpine.DEB.2.10.1406070930490.25930@nanos \
--to=tglx@linutronix.de \
--cc=bmouring@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome