From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, chuhu@redhat.com
Subject: Re: [RFC][PATCH] ppc: Implement save_stack_trace_regs()
Date: Mon, 11 Jan 2016 09:57:29 -0500 [thread overview]
Message-ID: <20160111095729.77efd8e5@gandalf.local.home> (raw)
In-Reply-To: <1452483031.31943.6.camel@ellerman.id.au>
On Mon, 11 Jan 2016 14:30:31 +1100
Michael Ellerman <mpe@ellerman.id.au> wrote:
> Sorry, yep I'll take it.
>
> I trimmed the change log a bit, final version below.
>
> cheers
>
Thanks, appreciate it!
-- Steve
next prev parent reply other threads:[~2016-01-11 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 18:50 [RFC][PATCH] ppc: Implement save_stack_trace_regs() Steven Rostedt
2015-12-09 0:20 ` Michael Ellerman
2015-12-09 0:28 ` Steven Rostedt
2015-12-09 1:03 ` Michael Ellerman
2015-12-09 1:21 ` Steven Rostedt
2015-12-16 17:24 ` Steven Rostedt
2016-01-08 22:50 ` Steven Rostedt
2016-01-11 3:30 ` Michael Ellerman
2016-01-11 14:57 ` Steven Rostedt [this message]
2016-01-12 12:32 ` powerpc: Implement save_stack_trace_regs() to enable kprobe stack tracing (was [RFC] ppc: Implement save_stack_trace_regs()) Michael Ellerman
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=20160111095729.77efd8e5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chuhu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).