From: John Ogness <john.ogness@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
jbaron@akamai.com, mingo@redhat.com, kernel@axis.com,
corbet@lwn.net, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] dynamic debug: allow printing to trace event
Date: Thu, 23 Jul 2020 16:26:23 +0206 [thread overview]
Message-ID: <878sfacnyw.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87blk6cosb.fsf@jogness.linutronix.de>
On 2020-07-23, John Ogness <john.ogness@linutronix.de> wrote:
> For me a trace event represents a specific point in the kernel
> code.
Actually, after revisiting Vincent's original patch (adding a "dynamic"
event in the "printk" group and placing the event within the
dynamic_printk printing path), I would fully support the new event. It
_is_ appropriately a printk/dynamic event.
John Ogness
next prev parent reply other threads:[~2020-07-23 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 14:11 [PATCH] dynamic debug: allow printing to trace event Vincent Whitchurch
2020-07-21 21:30 ` Steven Rostedt
2020-07-22 11:37 ` Sergey Senozhatsky
2020-07-22 13:52 ` John Ogness
2020-07-22 14:49 ` Vincent Whitchurch
2020-07-22 15:28 ` Steven Rostedt
2020-07-23 10:57 ` Vincent Whitchurch
2020-07-23 15:26 ` Steven Rostedt
2020-08-14 13:34 ` Vincent Whitchurch
2020-07-22 15:25 ` Steven Rostedt
2020-07-23 14:02 ` John Ogness
2020-07-23 14:20 ` John Ogness [this message]
2020-07-23 15:39 ` Steven Rostedt
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=878sfacnyw.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=vincent.whitchurch@axis.com \
/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