linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Wu XiangCheng <bobwxc@email.cn>
Cc: Stephen Boyd <swboyd@chromium.org>, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs: kernel-hacking: Fix two ref links
Date: Thu, 13 May 2021 09:37:33 -0600	[thread overview]
Message-ID: <87wns263wi.fsf@meer.lwn.net> (raw)
In-Reply-To: <2b855d05ab1da0635b88bfb8e65cac36260fba64.1618933932.git.bobwxc@email.cn>

Wu XiangCheng <bobwxc@email.cn> writes:

> Fix a abnormal funxtion ref link in locking.rst
> Convert a path to bare path
>
> Fixes: b1735296cef9 ("docs: locking: Drop :c:func: throughout")
> Signed-off-by: Wu XiangCheng <bobwxc@email.cn>
> ---
> v2:
> * No change.
>
> v1:
> <https://lore.kernel.org/linux-doc/6a15b17d46f5db190fb10afc57ea59132b33c701.1618761749.git.bobwxc@email.cn/>
>
>  Documentation/kernel-hacking/locking.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
> index ed1284c6f078..9bcd70aa8411 100644
> --- a/Documentation/kernel-hacking/locking.rst
> +++ b/Documentation/kernel-hacking/locking.rst
> @@ -1323,7 +1323,7 @@ from user context, and can sleep.
>  
>     -  put_user()
>  
> --  kmalloc(GP_KERNEL) <kmalloc>`
> +-  :c:func:`kmalloc(GFP_KERNEL) <kmalloc>`

So this makes no sense at all.  We are trying to get rid of :c:func:;
why are you adding it back?

Thanks,

jon

  reply	other threads:[~2021-05-13 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 16:01 [PATCH v2 1/2] docs/zh_CN: Add translation zh_CN/kernel-hacking/locking.rst Wu XiangCheng
2021-04-20 16:02 ` [PATCH v2 2/2] docs: kernel-hacking: Fix two ref links Wu XiangCheng
2021-05-13 15:37   ` Jonathan Corbet [this message]
2021-05-13 18:48     ` Wu X.C.

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=87wns263wi.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bobwxc@email.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=swboyd@chromium.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).