From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc <linux-doc@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 00/11] docs/mm: add boot time memory management docs
Date: Mon, 2 Jul 2018 11:32:55 -0600 [thread overview]
Message-ID: <20180702113255.1f7504e2@lwn.net> (raw)
In-Reply-To: <1530370506-21751-1-git-send-email-rppt@linux.vnet.ibm.com>
On Sat, 30 Jun 2018 17:54:55 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> Both bootmem and memblock have pretty good documentation coverage. With
> some fixups and additions we get a nice overall description.
>
> v2 changes:
> * address Randy's comments
>
> Mike Rapoport (11):
> mm/bootmem: drop duplicated kernel-doc comments
> docs/mm: nobootmem: fixup kernel-doc comments
> docs/mm: bootmem: fix kernel-doc warnings
> docs/mm: bootmem: add kernel-doc description of 'struct bootmem_data'
> docs/mm: bootmem: add overview documentation
> mm/memblock: add a name for memblock flags enumeration
> docs/mm: memblock: update kernel-doc comments
> docs/mm: memblock: add kernel-doc comments for memblock_add[_node]
> docs/mm: memblock: add kernel-doc description for memblock types
> docs/mm: memblock: add overview documentation
> docs/mm: add description of boot time memory management
So this seems like good stuff overall. It digs pretty deeply into the mm
code, though, so I'm a little reluctant to apply it without an ack from an
mm developer. Alternatively, I'm happy to step back if Andrew wants to
pick the set up.
Thanks,
jon
next prev parent reply other threads:[~2018-07-02 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 14:54 [PATCH v2 00/11] docs/mm: add boot time memory management docs Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 01/11] mm/bootmem: drop duplicated kernel-doc comments Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 02/11] docs/mm: nobootmem: fixup " Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 03/11] docs/mm: bootmem: fix kernel-doc warnings Mike Rapoport
2018-06-30 14:54 ` [PATCH v2 04/11] docs/mm: bootmem: add kernel-doc description of 'struct bootmem_data' Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 05/11] docs/mm: bootmem: add overview documentation Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 06/11] mm/memblock: add a name for memblock flags enumeration Mike Rapoport
2018-07-12 8:00 ` Michal Hocko
2018-06-30 14:55 ` [PATCH v2 07/11] docs/mm: memblock: update kernel-doc comments Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 08/11] docs/mm: memblock: add kernel-doc comments for memblock_add[_node] Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 09/11] docs/mm: memblock: add kernel-doc description for memblock types Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 10/11] docs/mm: memblock: add overview documentation Mike Rapoport
2018-06-30 14:55 ` [PATCH v2 11/11] docs/mm: add description of boot time memory management Mike Rapoport
2018-07-03 12:23 ` Michal Hocko
2018-07-12 7:26 ` Mike Rapoport
2018-07-01 15:26 ` [PATCH v2 00/11] docs/mm: add boot time memory management docs Randy Dunlap
2018-07-02 17:32 ` Jonathan Corbet [this message]
2018-07-18 11:47 ` Mike Rapoport
2018-07-18 12:02 ` Jonathan Corbet
2018-07-18 17:00 ` Mike Rapoport
2018-07-26 21:45 ` Jonathan Corbet
2018-08-02 18:36 ` Jonathan Corbet
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=20180702113255.1f7504e2@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).