linux-kernel - Re: [PATCH v2 00/11] docs/mm: add boot time memory management docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180718114730.GD4302@rapoport-lnx>
Date:   Wed, 18 Jul 2018 14:47:30 +0300
From:   Mike Rapoport <rppt@...ux.vnet.ibm.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        linux-doc <linux-doc@...r.kernel.org>,
        linux-mm <linux-mm@...ck.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 00/11] docs/mm: add boot time memory management docs

Hi,

On Mon, Jul 02, 2018 at 11:32:55AM -0600, Jonathan Corbet wrote:
> On Sat, 30 Jun 2018 17:54:55 +0300
> Mike Rapoport <rppt@...ux.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.

Jon, does Michal's reply [1] address your concerns?
Or should I respin and ask Andrew to pick it up? 

[1] https://lore.kernel.org/lkml/20180712080006.GA328@dhcp22.suse.cz/
> Thanks,
> 
> jon
> 

-- 
Sincerely yours,
Mike.