From: Randy Dunlap <rdunlap@infradead.org>
To: Matthew Wilcox <willy@infradead.org>, John Hubbard <jhubbard@nvidia.com>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] mm,doc: Add new documentation structure
Date: Wed, 4 May 2022 21:43:04 -0700 [thread overview]
Message-ID: <7628c3d7-9b5a-f3b1-1a05-a348e701c171@infradead.org> (raw)
In-Reply-To: <YnLiKnVdBFYLtCJe@casper.infradead.org>
On 5/4/22 13:29, Matthew Wilcox wrote:
> On Wed, May 04, 2022 at 06:12:09AM -0700, John Hubbard wrote:
>> This needs to be properly merged with the existing index. Otherwise
>> the result here is very confusing because there are two summaries
>> and no explanation of what is going on here.
>>
>> If I get a moment today, I'll take a quick shot at at merging them,
>> and post some suggestions here, but just wanted to point that out
>> before this goes in as-is.
>
> John and I have chatted to understand what he was getting at here,
> but haven't had a chance to review this change in-person yet.
>
> +++ b/Documentation/vm/index.rst
> @@ -2,6 +2,9 @@
> Linux Memory Management Documentation
> =====================================
>
> +Memory Management Guide
> +=======================
> +
> This is a guide to understanding the memory management subsystem
> of Linux. If you are looking for advice on simply allocating memory,
> see the :ref:`memory_allocation`. For controlling and tuning guides,
> @@ -24,10 +27,14 @@ see the :doc:`admin guide <../admin-guide/mm/index>`.
> shmfs
> oom
>
> -This is a collection of documents about the Linux memory management (mm)
> -subsystem internals with different level of details ranging from notes and
> -mailing list responses for elaborating descriptions of data structures and
> -algorithms.
> +Legacy Documentation
> +====================
> +
> +This is a collection of older documents about the Linux memory management
> +(mm) subsystem internals with different level of details ranging from
I prefer (MM).
Otherwise LGTM.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> +notes and mailing list responses for elaborating descriptions of data
> +structures and algorithms. It should all be integrated nicely into the
> +above structured documentation, or deleted if it has served its purpose.
>
> .. toctree::
> :maxdepth: 1
>
--
~Randy
next prev parent reply other threads:[~2022-05-05 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 6:30 [PATCH] mm,doc: Add new documentation structure Matthew Wilcox (Oracle)
2022-05-04 6:30 ` Bagas Sanjaya
2022-05-04 16:58 ` Matthew Wilcox
2022-05-04 13:12 ` John Hubbard
2022-05-04 17:01 ` Matthew Wilcox
2022-05-04 20:29 ` Matthew Wilcox
2022-05-05 0:39 ` John Hubbard
2022-05-05 4:43 ` Randy Dunlap [this message]
2022-05-05 4:49 ` Matthew Wilcox
2022-05-06 21:10 ` Johannes Weiner
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=7628c3d7-9b5a-f3b1-1a05-a348e701c171@infradead.org \
--to=rdunlap@infradead.org \
--cc=jhubbard@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).