linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] docs/core-api: memory-allocation: remove uses of c:func:
Date: Thu, 24 Oct 2019 12:02:27 -0600	[thread overview]
Message-ID: <20191024120227.0bd1ae92@lwn.net> (raw)
In-Reply-To: <20191022211438.3938-2-chris.packham@alliedtelesis.co.nz>

On Wed, 23 Oct 2019 10:14:37 +1300
Chris Packham <chris.packham@alliedtelesis.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@alliedtelesis.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?

Thanks,

jon

  reply	other threads:[~2019-10-24 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 21:14 [PATCH v2 0/2] docs/core-api: memory-allocation: minor cleanups Chris Packham
2019-10-22 21:14 ` [PATCH v2 1/2] docs/core-api: memory-allocation: remove uses of c:func: Chris Packham
2019-10-24 18:02   ` Jonathan Corbet [this message]
2019-10-24 19:39     ` Chris Packham
2019-10-24 19:49       ` Randy Dunlap
2019-10-22 21:14 ` [PATCH v2 2/2] docs/core-api: memory-allocation: mention size helpers Chris Packham

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=20191024120227.0bd1ae92@lwn.net \
    --to=corbet@lwn.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).