[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260109095858.3401c4d9@gandalf.local.home>
Date: Fri, 9 Jan 2026 09:58:58 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: "Dr. David Alan Gilbert" <dave@...blig.org>, Julia Lawall
<julia.lawall@...ia.fr>, Theodore Tso <tytso@....edu>, Sasha Levin
<sashal@...nel.org>, Gabriele Paoloni <gpaoloni@...hat.com>, Kate Stewart
<kstewart@...uxfoundation.org>, Chuck Wolber <chuckwolber@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>, Mark Rutland <mark.rutland@....com>,
Thomas Gleixner <tglx@...utronix.de>, Lorenzo Stoakes
<lorenzo.stoakes@...cle.com>, Shuah Khan <skhan@...uxfoundation.org>, Chris
Mason <clm@...a.com>, linux-kernel@...r.kernel.org
Subject: Re: Follow-up on Linux-kernel code accessibility
On Thu, 8 Jan 2026 17:34:14 -0800
"Paul E. McKenney" <paulmck@...nel.org> wrote:
> Had you instead sent me a separate email asking about this constant,
> I would likely have just answered. I would imagine that Joel would have
> done the same in response to your asking him.
OK so this is part of the contention here. This thread turned slightly away
from the original topic and moved towards the importance of commenting
code, at least for me. But if you were still discussing this as a
requirement document of some kind, then the comment on the "3" is out of
scope.
-- Steve
Powered by blists - more mailing lists