From: Steven Rostedt <rostedt@goodmis.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Tom Zanussi <zanussi@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] tracing: support dynamic string field types for synthetic events
Date: Fri, 25 Sep 2020 15:27:09 -0400 [thread overview]
Message-ID: <20200925152709.6f73b4a2@oasis.local.home> (raw)
In-Reply-To: <20200925190806.1870935-1-axelrasmussen@google.com>
On Fri, 25 Sep 2020 12:08:05 -0700
Axel Rasmussen <axelrasmussen@google.com> wrote:
> Hi Steven and Tom,
>
> In this thread: https://lkml.org/lkml/2020/9/17/1015 we discussed how to plumb
> dynamic strings into synthetic events. Tom, you proposed adding a new dynamic
> string type to synthetic event definition like "char foo[]".
Thanks Axel,
As this is Tom's code, I'll let him give his review.
-- Steve
next prev parent reply other threads:[~2020-09-25 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 19:08 Axel Rasmussen
2020-09-25 19:08 ` [RFC PATCH 1/1] " Axel Rasmussen
2020-09-25 19:53 ` Tom Zanussi
2020-09-25 19:27 ` Steven Rostedt [this message]
2020-09-25 19:48 ` [RFC PATCH 0/1] " Tom Zanussi
2020-09-25 20:57 ` Axel Rasmussen
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=20200925152709.6f73b4a2@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@kernel.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®