From: Bradley Morgan <brads@mainlining.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] tracing/user_events: Clear copied tracing state before fork duplication
Date: Thu, 27 Aug 2026 13:44:13 +0100 [thread overview]
Message-ID: <E35157CB-DB14-4195-87A5-FD411D9E464A@mainlining.org> (raw)
In-Reply-To: <20260827084306.54c13b60@gandalf.local.home>
On 27 August 2026 13:43:06 BST, Steven Rostedt <rostedt@goodmis.org> wrote:
>On Thu, 27 Aug 2026 13:29:20 +0100
>Bradley Morgan <brads@mainlining.org> wrote:
>
>> I review on
>>
>>
>> 1: does this do what it's intended
>> 2: does it fix X?
>> 3: Any comments, any new functions used instead, any way to get the line
>count shorter?
>>
>>
>> And others, I apologise if I'm wrong. I just review in a different
>style.
>
>Please just focus on correctness, until you understand what the
>maintainer's preferences are.
>
Yep, I already do, I focus on if the code is actually correct too.
So don't panic. :)
>-- Steve
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
next prev parent reply other threads:[~2026-08-27 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 21:44 [PATCH v2] tracing/user_events: Clear copied tracing state before fork duplication Jérémy Jean
2026-08-26 22:37 ` Bradley Morgan
2026-08-27 7:15 ` Jérémy Jean
2026-08-27 9:45 ` Bradley Morgan
2026-08-27 12:15 ` Steven Rostedt
2026-08-27 12:17 ` Bradley Morgan
2026-08-27 12:08 ` Steven Rostedt
2026-08-27 12:09 ` Bradley Morgan
2026-08-27 12:19 ` Steven Rostedt
2026-08-27 12:24 ` Bradley Morgan
2026-08-27 12:27 ` Jérémy Jean
2026-08-27 12:29 ` Bradley Morgan
2026-08-27 12:43 ` Steven Rostedt
2026-08-27 12:44 ` Bradley Morgan [this message]
2026-08-27 12:42 ` Steven Rostedt
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=E35157CB-DB14-4195-87A5-FD411D9E464A@mainlining.org \
--to=brads@mainlining.org \
--cc=jeremy.jean@oss.cyber.gouv.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.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