From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: "mhiramat@kernel.org" <mhiramat@kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"beaub@linux.microsoft.com" <beaub@linux.microsoft.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] tracing/user_events: Share state with existing threads
Date: Thu, 12 Nov 2026 04:25:06 -0500 [thread overview]
Message-ID: <20261112042506.0fca0524@fedora> (raw)
In-Reply-To: <40C83F97-D53F-4050-9CE4-19449912FB20@getmailspring.com>
On Tue, 10 Nov 2026 17:50:03 -0500
Jeff Barnes <jeffbarnes@linux.microsoft.com> wrote:
> Hi Steve, Beau,
>
> Gentle ping on this v2 series. I don't have any outstanding changes to
> make at this point.
> Just to clarify, this is a separate patch from the Fail fork one.
> Please let me know if anything further is needed from my side.
>
Hi Jeff,
I'm currently traveling back home and will be taking the rest of the
week off. My backlog is a bit behind and I'm trying to get through
them. I do have a 4 hour layover, and I expect to work on triaging
patches. Hopefully I can get to yours, otherwise, it may have to wait
until next week.
-- Steve
prev parent reply other threads:[~2026-11-12 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 15:39 [PATCH 0/2] tracing/user_events: Share state between existing threads Jeff Barnes
2026-10-02 15:39 ` [PATCH 1/2] selftests/user_events: Test registration from " Jeff Barnes
2026-10-02 15:39 ` [PATCH 2/2] tracing/user_events: Share tracing state between " Jeff Barnes
2026-10-06 16:47 ` [PATCH v2 0/3] tracing/user_events: Share state with " Jeff Barnes
2026-10-06 16:47 ` [PATCH v2 1/3] tracing/user_events: Serialize duplicate enabler lookup with event removal Jeff Barnes
2026-10-06 16:47 ` [PATCH v2 2/3] tracing/user_events: Share event state with existing threads Jeff Barnes
2026-10-06 16:47 ` [PATCH v2 3/3] selftests/user_events: Test registration from " Jeff Barnes
2026-10-19 14:23 ` [PATCH v2 0/3] tracing/user_events: Share state with " Jeff Barnes
2026-10-19 14:39 ` Steven Rostedt
2026-11-10 22:50 ` Jeff Barnes
2026-11-12 9:25 ` 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=20261112042506.0fca0524@fedora \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=shuah@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