[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d053a8dc8e08b5b3ff4f2f4ff5b7c6ce4c3e773f.camel@alliedtelesis.co.nz>
Date: Thu, 24 Oct 2019 19:39:36 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: "corbet@....net" <corbet@....net>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] docs/core-api: memory-allocation: remove uses of
c:func:
Hi Jon,
On Thu, 2019-10-24 at 12:02 -0600, Jonathan Corbet wrote:
> On Wed, 23 Oct 2019 10:14:37 +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(-)
>
> So I can't get this patch to apply, and I can't even figure out why. If
> you take the patch from the list, can you apply it to a docs-next (or
> mainline) branch?
>
I think it might be dependent on my other typo fix patch[1]. I'll
rebase to v5.4-rc4 and send as a series of 3. Sorry for the hassle.
--
[1]
https://lore.kernel.org/lkml/20191021003833.15704-1-chris.packham@alliedtelesis.co.nz/
> Thanks,
>
> jon
Powered by blists - more mailing lists