[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251220040013.GA42033@macsyma.lan>
Date: Fri, 19 Dec 2025 23:00:13 -0500
From: "Theodore Tso" <tytso@....edu>
To: Chris Mason <clm@...a.com>
Cc: Julia Lawall <julia.lawall@...ia.fr>,
"Paul E. McKenney" <paulmck@...nel.org>,
Gabriele Paoloni <gpaoloni@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
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>,
Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Follow-up on Linux-kernel code accessibility
On Fri, Dec 19, 2025 at 04:05:33PM -0500, Chris Mason wrote:
> I recently pushed out changes that remove most of the process and focus
> more on kernel internals. So hopefully over time we can get to
> something that just documents kerneling in a way that is useful beyond
> LLMs.
One of the things which I found really interesting, and it was a bit
of revelation to me, was how much we could have text that could be
useful *both* as a documentations for humans, as well as instructions
to LLM's. So I think both are important/useful.
- Ted
Powered by blists - more mailing lists