From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs: Add define for ALL dynamic events
Date: Wed, 23 Feb 2022 20:52:17 -0500 [thread overview]
Message-ID: <20220223205217.2d7ea5b0@rorschach.local.home> (raw)
In-Reply-To: <20220214080241.634290-1-tz.stoyanov@gmail.com>
On Mon, 14 Feb 2022 10:02:41 +0200
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> Some of the tracefs APIs for dynamic events accept bitmask of events. If
> a caller wants to address all types of events, it should list them in
> the bitmask. This logic is fragile. When a new type of dynamic event is
> introduced, the API callers should be modified. That's why a new define
> is added, part of the library API, to address all types of dynamic
> events.
>
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
And of course, after I release 1.3, I discovered I forgot about this patch :-p
Well, it's usually a tradition to release a .1 right after a .0 due to
something stupid I did :-/
-- Steve
prev parent reply other threads:[~2022-02-24 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 8:02 [PATCH] libtracefs: Add define for ALL dynamic events Tzvetomir Stoyanov (VMware)
2022-02-24 1:52 ` Steven Rostedt [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=20220223205217.2d7ea5b0@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.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;
as well as URLs for NNTP newsgroup(s).