From: Steven Rostedt <rostedt@goodmis.org>
To: Metin Kaya <metin.kaya@arm.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH] libtracefs: Destroy synthetic and eprobes before other events
Date: Tue, 19 Nov 2024 22:57:37 -0500 [thread overview]
Message-ID: <20241119225737.1a19a573@rorschach.local.home> (raw)
In-Reply-To: <cf4686b0-5e1e-4839-9484-7611e288f4b7@arm.com>
On Fri, 18 Oct 2024 15:51:20 +0100
Metin Kaya <metin.kaya@arm.com> wrote:
> I've these patches in my stash:
>
> * 8468f2e - (HEAD -> libtracefs) libtracefs utest: Add debug logs <Metin
> Kaya>
> * cee05c1 - libtracefs utest: Do not test more events than what the ring
> buffer can hold <Steven Rostedt (Google)>
> * 385650c - libtracefs utest: Fix min percent test <Steven Rostedt (Google)>
> * c0810b9 - libtracefs utest: Add test to check handling multiple
> dynamic events <Steven Rostedt (Google)>
> * d8fcfff - libtracefs: Destroy synthetic and eprobes before other
> events <Steven Rostedt (Google)>
> * 78d8d2e - (origin/libtracefs, origin/HEAD) libtracefs: Have
> tracefs_dynevent_get_all() find kprobes and uprobes properly <Steven
> Rostedt (Google)>
I haven't applied this patch yet (but plan to). Is this still an issue
for you?
-- Steve
next prev parent reply other threads:[~2024-11-20 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 16:35 [PATCH] libtracefs: Destroy synthetic and eprobes before other events Steven Rostedt
2024-10-17 8:38 ` Metin Kaya
2024-10-17 20:01 ` Steven Rostedt
2024-10-18 9:13 ` Metin Kaya
2024-10-18 14:17 ` Steven Rostedt
2024-10-18 14:51 ` Metin Kaya
2024-11-20 3:57 ` Steven Rostedt [this message]
2024-11-20 7:42 ` Metin Kaya
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=20241119225737.1a19a573@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=metin.kaya@arm.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).