From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2 v2] tracing: Enable tracepoints early and allow printk to use them
Date: Mon, 15 Dec 2014 16:10:51 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1412151610050.17382@nanos> (raw)
In-Reply-To: <20141214201609.126831471@goodmis.org>
On Sun, 14 Dec 2014, Steven Rostedt wrote:
> As the merge window is still open, and this code was not as complex
> as I thought it might be. I'm thinking of pushing this in now.
>
> This will allow Thomas to debug his irq work for 3.20.
>
> This code is not that intrusive and I'm currently running it through
> all my tests. But I like to have some more eyes on this, as I don't
> like to push something into mainline this quickly. I'm doing this only
> because the code is simple enough and is useful for work coming in 3.20.
>
> I also feel that I could handle the fall out of this work over the
> holidays if need be.
Works like a charm.
Tested-and-acked-by: Thomas Gleixner <tglx@linutronix.de>
prev parent reply other threads:[~2014-12-15 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 20:16 Steven Rostedt
2014-12-14 20:16 ` [PATCH 1/2 v2] tracing: Move enabling tracepoints to just after rcu_init() Steven Rostedt
2014-12-14 22:21 ` Paul E. McKenney
2014-12-14 20:16 ` [PATCH 2/2 v2] tracing: Add tp_printk cmdline to have tracepoints go to printk() Steven Rostedt
2014-12-14 20:29 ` [PATCH 0/2 v2] tracing: Enable tracepoints early and allow printk to use them Steven Rostedt
2014-12-15 15:10 ` Thomas Gleixner [this message]
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.11.1412151610050.17382@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®