From: "Paul E. McKenney" <paulmck@kernel.org>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Josh Triplett <josh@joshtriplett.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
rcu@vger.kernel.org, clm@meta.com
Subject: Re: [PATCH] rcutorture: Fix operator precedence bug in exp_current() invocation
Date: Tue, 23 Dec 2025 09:28:22 -0800 [thread overview]
Message-ID: <52bda0a7-5311-4e62-89c5-287c731548e4@paulmck-laptop> (raw)
In-Reply-To: <f99bbb2e-62bd-47fb-8cee-07716766c087@nvidia.com>
On Tue, Dec 23, 2025 at 12:22:51PM -0500, Joel Fernandes wrote:
> On 12/23/2025 11:37 AM, Steven Rostedt wrote:
> > On Mon, 22 Dec 2025 17:12:18 -0800
> > "Paul E. McKenney" <paulmck@kernel.org> wrote:
> >
> >> Good eyes, thank you!
> >>
> >> Unfortunately, Chris Mason beat you to it:
> >
> > Was it Chris or his AI? ;-)
>
> Does it matter? It is like saying, was it "Chris or his text editor". ;-)
Adding Chris on CC for his thoughts on whether it was him or his AI and
whether or not this matters. Should he choose to share any thoughts on
either topic. ;-)
Thanx, Paul
next prev parent reply other threads:[~2025-12-23 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 0:44 Joel Fernandes
2025-12-23 1:12 ` Paul E. McKenney
2025-12-23 1:24 ` Joel Fernandes
2025-12-23 16:37 ` Steven Rostedt
2025-12-23 17:22 ` Joel Fernandes
2025-12-23 17:28 ` Paul E. McKenney [this message]
2025-12-23 17:30 ` Joel Fernandes
2025-12-23 17:51 ` Paul E. McKenney
2025-12-23 20:54 ` Steven Rostedt
2025-12-23 23:50 ` Paul E. McKenney
2025-12-24 14:14 ` Steven Rostedt
2025-12-25 18:43 ` Paul E. McKenney
2025-12-24 0:50 ` Chris Mason
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=52bda0a7-5311-4e62-89c5-287c731548e4@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=clm@meta.com \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®