Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "David Hildenbrand (Arm)" <david@kernel.org>, linux-doc@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Matthew Wilcox <willy@infradead.org>,
	Harry Yoo <harry@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/mm: clarify that we are not looking for LLM generated content
Date: Tue, 23 Jun 2026 14:33:17 -0600	[thread overview]
Message-ID: <87mrwlatf6.fsf@trenco.lwn.net> (raw)
In-Reply-To: <1cbdb3a3-b8db-4ae2-aa66-9042c1033745@kernel.org>

"David Hildenbrand (Arm)" <david@kernel.org> writes:

>>> I assume this was not picked up yet? (via documentation or mm tree?)
>> 
>> I had figured Andrew would grab it; I can certainly do so if you'd like.
>
> yes please. I guess I'll soon start grabbing stuff myself. Stay tuned. :)

OK, done.

Let me know how you would like to handle things going forward.  I'm
happy to pick up MM docs changes or to leave them for you, whatever
works best.

Thanks,

jon

      reply	other threads:[~2026-06-23 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 21:03 [PATCH] docs/mm: clarify that we are not looking for LLM generated content David Hildenbrand (Arm)
2026-04-20 23:45 ` SeongJae Park
2026-04-21  0:04 ` Harry Yoo (Oracle)
2026-04-21  6:45 ` Mike Rapoport
2026-04-21  7:38 ` Lorenzo Stoakes
2026-04-21  8:26 ` Vlastimil Babka (SUSE)
2026-04-21 15:15 ` Zi Yan
2026-04-23 11:55 ` Michal Hocko
2026-04-23 12:04 ` Dev Jain
2026-06-23  8:15 ` David Hildenbrand (Arm)
2026-06-23 12:59   ` Jonathan Corbet
2026-06-23 13:56     ` David Hildenbrand (Arm)
2026-06-23 20:33       ` Jonathan Corbet [this message]

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=87mrwlatf6.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=harry@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.org \
    /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