From: Jonathan Corbet <corbet@lwn.net>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v5] Documentation/mm: Initial page table documentation
Date: Sun, 18 Jun 2023 12:54:55 -0600 [thread overview]
Message-ID: <87zg4wvbwg.fsf@meer.lwn.net> (raw)
In-Reply-To: <3045029.CbtlEUcBR6@suse>
"Fabio M. De Francesco" <fmdefrancesco@gmail.com> writes:
> I question the target audience of this documentation. How can we expect any
> developer working with Linux to be unaware of such basic concepts? Adding
> documentation about these foundational concepts would create a precedent,
> potentially leading to further documentation on other fundamental abstractions
> like "task," "multi-threading," and "scheduling" – concepts that are integral
> to kernel management. The inclusion of such basic topics could quickly clutter
> up the specialized Linux kernel documentation.
Someday, if we find ourselves in the position of having too much
documentation, we can entertain patches to clean out material that is
deemed to be too elementary for kernel developers. Before then, though,
if we are worried about clutter, we may want to put more effort into
addressing the large amount of duplicated and obsolete documentation in
the kernel now.
Until then, I see no reason to oppose the addition of material that,
even if you don't personally find it helpful, may indeed be helpful to
developers trying to come up to speed on just what the kernel is doing.
Thanks,
jon
next prev parent reply other threads:[~2023-06-18 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:25 Linus Walleij
2023-06-16 14:14 ` Jonathan Corbet
2023-06-18 13:16 ` Fabio M. De Francesco
2023-06-18 18:54 ` Jonathan Corbet [this message]
2023-06-19 8:16 ` Linus Walleij
2023-06-21 1:10 ` Fabio M. De Francesco
2023-06-21 7:35 ` Linus Walleij
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=87zg4wvbwg.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=fmdefrancesco@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@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