linux-kernel - Re: [PATCH v3 2/3] docs/core-api: memory-allocation: remove uses of c:func:

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: <1ddbd3045d6a989b32065c0bd5b3a3c0ef525953.camel@alliedtelesis.co.nz>
Date:   Thu, 24 Oct 2019 20:51:23 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     "corbet@....net" <corbet@....net>
CC:     "rppt@...ux.ibm.com" <rppt@...ux.ibm.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "willy@...radead.org" <willy@...radead.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] docs/core-api: memory-allocation: remove uses of
 c:func:

Hi Jon,

On Thu, 2019-10-24 at 14:29 -0600, Jonathan Corbet wrote:
> On Fri, 25 Oct 2019 08:50:15 +1300
> Chris Packham <chris.packham@...iedtelesis.co.nz> wrote:
> 
> > These are no longer needed as the documentation build will automatically
> > add the cross references.
> > 
> > Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
> > ---
> > 
> > Notes:
> >     It should be noted that kvmalloc() and kmem_cache_destroy() lack a
> >     kerneldoc header, a side-effect of this change is that the :c:func:
> >     fallback of making them bold is lost. This is probably best fixed by
> >     adding a kerneldoc header to their source.
> >     
> >     Changes in v2:
> >     - new
> > 
> >  Documentation/core-api/memory-allocation.rst | 49 +++++++++-----------
> >  1 file changed, 23 insertions(+), 26 deletions(-)
> 
> This one still doesn't apply; have you verified that you can apply the
> whole series to docs-next?

I can see the problem. I'll rebase against docs-next and send a v4.

When I do actually get a series that applies to docs-next it'll
conflict with 59bb47985c1d ("mm, sl[aou]b: guarantee
natural alignment for kmalloc(power-of-two)") in Linus's tree.



> 
> Thanks,
> 
> jon