mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	joe@perches.com, vincent.whitchurch@axis.com
Cc: jbaron@akamai.com, Ingo Molnar <mingo@redhat.com>,
	drinkcat@chromium.org, kernel@axis.com,
	"corbet@lwn.net" <corbet@lwn.net>, Petr Mladek <pmladek@suse.com>,
	sergey.senozhatsky@gmail.com, john.ogness@linutronix.de,
	linux-kernel <linux-kernel@vger.kernel.org>,
	gpiccoli@igalia.com
Subject: Re: Re: [PATCH v3 2/2] dynamic debug: allow printing to trace event
Date: Tue, 26 Dec 2023 13:57:30 -0300	[thread overview]
Message-ID: <1c54063e-8ad2-5be3-85fe-519f5a944d20@igalia.com> (raw)
In-Reply-To: <9bfb4c4bd1415a8ce527a913730672508a8e8330.camel@perches.com>

[First of all, apologies for necro'ing this thread - for those that
somehow deleted the full thread of their clients, here is the link:
https://lore.kernel.org/lkml/20200825153338.17061-1-vincent.whitchurch@axis.com/]

So, I would like to reopen this discussion. Is there any reason this
feature wasn't merged Joe? Can we improve something in order to get it
into mainline?

I'm saying that 'cause I almost implemented this myself here, I have the
same use case as Vicent's - but thankfully, I searched before and he
already implemented that. As per my understanding, there was no
objection from Steven, right?

Thanks in advance! And happy holidays =)
Cheers,


Guilherme

  parent reply	other threads:[~2023-12-26 17:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 15:33 [PATCH v3 0/2] Dynamic debug trace support Vincent Whitchurch
2020-08-25 15:33 ` [PATCH v3 1/2] dynamic debug: split enable and printk flags Vincent Whitchurch
2020-08-25 15:33 ` [PATCH v3 2/2] dynamic debug: allow printing to trace event Vincent Whitchurch
2020-08-25 15:53   ` Joe Perches
2020-08-26 19:32     ` Steven Rostedt
2020-08-26 19:53       ` Joe Perches
2020-09-02 12:17         ` Vincent Whitchurch
2023-12-26 16:57         ` Guilherme G. Piccoli [this message]
2023-12-27  8:29           ` Vincent Whitchurch
2023-12-27 13:06             ` Guilherme G. Piccoli

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=1c54063e-8ad2-5be3-85fe-519f5a944d20@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=corbet@lwn.net \
    --cc=drinkcat@chromium.org \
    --cc=jbaron@akamai.com \
    --cc=joe@perches.com \
    --cc=john.ogness@linutronix.de \
    --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
all inboxes | Powered by JetHome®