From: Mike Galbraith <bitbucket@online.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Manfred Spraul <manfred@colorfullife.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH RT] rt,ipc,sem: fix -rt livelock
Date: Fri, 13 Sep 2013 06:48:21 +0200 [thread overview]
Message-ID: <1379047701.5455.101.camel@marge.simpson.net> (raw)
In-Reply-To: <20130912233339.4c57be5c@gandalf.local.home>
On Thu, 2013-09-12 at 23:33 -0400, Steven Rostedt wrote:
> Can you repost as a patch series please.
Sure, will do.
-Mike
next prev parent reply other threads:[~2013-09-13 4:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 21:33 [PATCH RT 0/3] hwlat-detector: Have it actually find hardware latency Steven Rostedt
2013-08-19 21:33 ` [PATCH RT 1/3] hwlat-detector: Update hwlat_detector to add outer loop detection Steven Rostedt
2013-08-19 21:33 ` [PATCH RT 2/3] hwlat-detector: Use trace_clock_local if available Steven Rostedt
2013-08-19 21:33 ` [PATCH RT 3/3] hwlat-detector: Use thread instead of stop machine Steven Rostedt
2013-08-21 15:59 ` [PATCH RT 0/3] hwlat-detector: Have it actually find hardware latency Sebastian Andrzej Siewior
2013-08-30 5:57 ` [PATCH RT] hwlat-detector: Don't ignore threshold module parameter Mike Galbraith
2013-08-30 14:39 ` [PATCH RT] rt,ipc,sem: fix -rt livelock Mike Galbraith
2013-08-31 5:27 ` Mike Galbraith
2013-09-06 7:08 ` Mike Galbraith
2013-09-10 6:30 ` Mike Galbraith
2013-09-11 14:03 ` Manfred Spraul
2013-09-12 7:40 ` Mike Galbraith
2013-09-12 19:15 ` Steven Rostedt
2013-09-13 3:20 ` Mike Galbraith
2013-09-13 3:33 ` Steven Rostedt
2013-09-13 4:48 ` Mike Galbraith [this message]
2013-09-13 4:36 ` Mike Galbraith
2013-09-13 12:56 ` Mike Galbraith
2013-09-12 18:23 ` [PATCH RT] hwlat-detector: Don't ignore threshold module parameter Steven Rostedt
2013-10-04 10:30 ` Sebastian Andrzej Siewior
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=1379047701.5455.101.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=a.p.zijlstra@chello.nl \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).