[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <069eff26-d5fc-4b09-aedb-079ea9ad156f@paulmck-laptop>
Date: Fri, 9 Jan 2026 10:31:52 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Steven Rostedt <rostedt@...dmis.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 Fri, Jan 09, 2026 at 09:58:58AM -0500, Steven Rostedt wrote:
> 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.
Thank you!
And I should re-emphasize that I really would like to see things that
add more robustness to the Linux kernel, including things that allow
it to be used in more demanding application areas.
I just want those things to be maintainable. Easy for me to say,
I know! ;-)
Thanx, Paul
Powered by blists - more mailing lists