From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: mhiramat@kernel.org, shuah@kernel.org, beaub@linux.microsoft.com,
mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] tracing/user_events: Share state with existing threads
Date: Mon, 19 Oct 2026 10:39:57 -0400 [thread overview]
Message-ID: <20261019103957.69759ee3@gandalf.local.home> (raw)
In-Reply-To: <20261019142301.2084882-1-jeffbarnes@linux.microsoft.com>
On Mon, 19 Oct 2026 10:23:01 -0400
Jeff Barnes <jeffbarnes@linux.microsoft.com> wrote:
> Gentle ping on this series.
>
> Please let me know if there are any further comments or changes you'd like me to make.
Hi Jeff,
FYI, always start a new thread when sending out a new series. Don't make it
a reply to an old one. That makes it confusing to know which series to look
at.
Also, I've was traveling between September 14th and October 10th and my
backlog built up quite a bit.
If Beau can review this series, that would be great. I'm currently putting
together several branches for the merge window. Unfortunately, due to my
backlog, there's patches that have been sent this month that will need to
be postponed to the next window.
As user_events are agnostic to other changes, there's still a chance your
changes can get added this window.
-- Steve
prev parent reply other threads:[~2026-10-19 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 15:39 [PATCH 0/2] tracing/user_events: Share state between " 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 [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=20261019103957.69759ee3@gandalf.local.home \
--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
all inboxes | Powered by JetHome®