linux-kernel - Re: [PATCH] docs/mm: Physical Memory: add "Memory map" section

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: <ZPiIJ0iuiqSpeG1P@casper.infradead.org>
Date:   Wed, 6 Sep 2023 15:09:43 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     Mike Rapoport <rppt@...nel.org>
Cc:     Jonathan Corbet <corbet@....net>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org
Subject: Re: [PATCH] docs/mm: Physical Memory: add "Memory map" section

On Wed, Sep 06, 2023 at 03:52:14PM +0300, Mike Rapoport wrote:
> On Wed, Sep 06, 2023 at 01:21:02PM +0100, Matthew Wilcox wrote:
> > I don't understand why you've done all this instead of linking to the
> > kernel-doc I wrote.
> 
> We can't have it both in Documentation/core-api/mm-api.rst and here without
> sphinx complaining: 

I didn't say "include it here", I said "link to it".

I don't see the value in documenting all of these structs here.  They
should be documented in the subsystem that actually uses them.  Just a
note that there's per-allocation data stored in struct page should be
enough, I think.