linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: 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 18:01:48 +0100	[thread overview]
Message-ID: <YnKxfAPkWQanHHGX@casper.infradead.org> (raw)
In-Reply-To: <20c73284-66e5-8e3a-aa78-01f982720aea@nvidia.com>

On Wed, May 04, 2022 at 06:12:09AM -0700, John Hubbard wrote:
> > @@ -2,12 +2,32 @@
> >   Linux Memory Management Documentation
> >   =====================================
> > +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,
> > +see the :doc:`admin guide <../admin-guide/mm/index>`.
> 
> 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.

Hm?  It reads OK to me the way I sent it out:

Linux Memory Management Documentation¶

This is a guide to understanding the memory management subsystem of
Linux. If you are looking for advice on simply allocating memory,
see the Memory Allocation Guide. For controlling and tuning guides,
see the admin guide.

[... list ...]

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.

[... another list ...]

> 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.

Happy to sit down with you in a free moment.  I have all this on my
laptop, including an htmldocs built version.


  reply	other threads:[~2022-05-04 17:01 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 [this message]
2022-05-04 20:29   ` Matthew Wilcox
2022-05-05  0:39     ` John Hubbard
2022-05-05  4:43     ` Randy Dunlap
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=YnKxfAPkWQanHHGX@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.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).