From: Mike Rapoport <rppt@kernel.org>
To: "David Hildenbrand (arm)" <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kit Dallege <xaum.io@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] Docs/mm: document Shared Memory Filesystem
Date: Sun, 15 Mar 2026 22:03:02 +0200 [thread overview]
Message-ID: <abcQdr4UD4znorRN@kernel.org> (raw)
In-Reply-To: <abcPusHClDoCeE4Y@kernel.org>
On Sun, Mar 15, 2026 at 10:00:00PM +0200, Mike Rapoport wrote:
> On Sun, Mar 15, 2026 at 08:50:04PM +0100, David Hildenbrand (arm) wrote:
> > On 3/14/26 19:17, Andrew Morton wrote:
> > > On Sat, 14 Mar 2026 17:02:47 +0100 Kit Dallege <xaum.io@gmail.com> wrote:
> > >
> > > > Hi Jon,
> > > >
> > > > The material was written with AI assistance (Claude) and then verified
> > > > against the source code in mm/shmem.c. I read through the implementation,
> > > > the existing comments, and Mel Gorman's book outline to identify what
> > > > should be covered, then used AI to help draft the prose, which I reviewed
> > > > and edited.
> > >
> > > OK, so you're saying that you created the content and used an LLM to
> > > assist in finishing it off?
> > >
> > > > I'm happy to rework anything that's inaccurate or doesn't meet the bar.
> > > > Should I add an Assisted-by tag to the commit?
> > >
> > > Yes, Assisted-by: is appropriate and useful here.
> > >
> > > From a quick scan, this material appears to be helpful and I think it
> > > would be good for us to get this into the tree in some fashion. Which
> > > will involve asking the relevant MM developers to review each change.
> >
> > So, someone with an LLM but no proven experience with the code produced some
> > doc, and maintainers/developers should dedicate their precious time to do
> > the hard work of checking everything?
>
> > I'm all for documenting stuff, especially if newcomers start exploring that
> > space by contributing small, carefully crafted documentation updates.
> >
> > It's then a good learning experience for someone that wants to work on the
> > code to really have to understand the code in detail, and what is actually
> > worth documenting (and what's an implementation detail).
> >
> > I see 7 doc updates for 7 different MM subsystems in my inbox, including
>
> Heh, it's wider:
> https://lore.kernel.org/all/?q=Kit+Dallege
>
> > So naturally, I get skeptical when it comes to "I read through the
> > implementation, the existing comments".
And another LLM says there are mistakes:
https://sashiko.dev/#/patchset/20260314152538.100593-1-xaum.io%40gmail.com
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-03-15 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 15:25 [PATCH] Docs/mm: document Shared Memory Filesystem Kit Dallege
2026-03-14 15:46 ` Jonathan Corbet
2026-03-14 16:02 ` Kit Dallege
2026-03-14 18:17 ` Andrew Morton
2026-03-14 18:38 ` Kit Dallege
2026-03-14 21:01 ` Hugh Dickins
2026-03-15 19:50 ` David Hildenbrand (arm)
2026-03-15 19:55 ` David Hildenbrand (arm)
2026-03-15 19:59 ` Mike Rapoport
2026-03-15 20:03 ` Mike Rapoport [this message]
2026-03-15 20:00 ` Lorenzo Stoakes (Oracle)
2026-03-15 20:14 ` Lorenzo Stoakes (Oracle)
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=abcQdr4UD4znorRN@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=xaum.io@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