From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Wu <michael@allwinnertech.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5] tracing: Fix race between update_event_fields and, event_define_fields
Date: Wed, 12 Aug 2026 09:51:06 -0400 [thread overview]
Message-ID: <20260812095106.6b2e76df@gandalf.local.home> (raw)
In-Reply-To: <f7b0e5a6-c38d-634e-4353-6d1bb5dcd12e@allwinnertech.com>
On Wed, 12 Aug 2026 10:14:24 +0800
Michael Wu <michael@allwinnertech.com> wrote:
> On 8/11/2026 9:00 PM, Steven Rostedt wrote:
> > This is still way too verbose. Is this AI written? If so, AI is *not* your friend.
> This commit was written by me, not by AI. I apologize for wasting your time. Thank you for rewriting the change.
Heh, AI tends to be very verbose, which is why I was thinking it was AI.
> > Why are the priorities of the notifiers important here?
> I probably wanted to describe the entire process, so I've gone on to say too much.
Yeah, adding more than what is needed distracts from the issue.
> > Less is more when it comes to describing a bug.
> Got it.
Great. And thanks for the fix.
-- Steve
prev parent reply other threads:[~2026-08-12 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 6:32 [PATCH v5] tracing: Fix race between update_event_fields and, event_define_fields Michael Wu
2026-08-10 14:45 ` Steven Rostedt
2026-08-11 6:00 ` Michael Wu
2026-08-11 13:00 ` Steven Rostedt
2026-08-12 2:14 ` Michael Wu
2026-08-12 13:51 ` 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=20260812095106.6b2e76df@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=michael@allwinnertech.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