From: Jonathan Corbet <corbet@lwn.net>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
Michal Hocko <mhocko@suse.com>
Cc: Kit Dallege <xaum.io@gmail.com>,
akpm@linux-foundation.org, david@kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Docs/mm: document the OOM killer
Date: Mon, 16 Mar 2026 09:06:07 -0600 [thread overview]
Message-ID: <87bjgnizkw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <31744315-bf9e-4d9a-9c25-63eef0bd2f01@lucifer.local>
"Lorenzo Stoakes (Oracle)" <ljs@kernel.org> writes:
> I wonder if some of us (I realise this sounds like self volunteering)
> should just write up some bare bones and patch it in, then we can get the
> iterating part of things moving?
That, of course, was the theory behind the addition of the skeleton
documentation that's there now :)
I have also thought about trying to fill it in once a bit of spare time
opens up. Funny how that tends not to happen, but I still would like to
do that at some point.
Michal's question, though, is something that needs a good answer: who is
the audience for Documentation/mm/ ? Some of the stuff in the patch
under discussion, if it were to reach an acceptable point, is probably
better placed in the admin guide. OTOH, a manual firmly aimed at people
trying to understand the MM code itself makes sense to me.
Thanks,
jon
prev parent reply other threads:[~2026-03-16 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 15:25 [PATCH] Docs/mm: document the OOM killer Kit Dallege
2026-03-15 20:48 ` Lorenzo Stoakes (Oracle)
2026-03-16 7:32 ` Michal Hocko
2026-03-16 14:16 ` Lorenzo Stoakes (Oracle)
2026-03-16 14:53 ` Michal Hocko
2026-03-16 15:06 ` 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=87bjgnizkw.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--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