All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu XiangCheng <bobwxc@email.cn>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Stephen Boyd <swboyd@chromium.org>, linux-doc@vger.kernel.org
Subject: [PATCH 2/2] docs: kernel-hacking: Fix two ref links
Date: Mon, 19 Apr 2021 00:11:30 +0800	[thread overview]
Message-ID: <6a15b17d46f5db190fb10afc57ea59132b33c701.1618761749.git.bobwxc@email.cn> (raw)
In-Reply-To: <26979ff9c52fe352f117204b3c5b939e4fe0c58d.1618761749.git.bobwxc@email.cn>

Fix a abnormal function ref link in locking.rst
Convert a path

Fixes: b1735296cef9 ("docs: locking: Drop :c:func: throughout")
Signed-off-by: Wu XiangCheng <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>`
 
 -  mutex_lock_interruptible() and
    mutex_lock()
@@ -1364,7 +1364,7 @@ Futex API reference
 Further reading
 ===============
 
--  ``Documentation/locking/spinlocks.rst``: Linus Torvalds' spinlocking
+-  Documentation/locking/spinlocks.rst: Linus Torvalds' spinlocking
    tutorial in the kernel sources.
 
 -  Unix Systems for Modern Architectures: Symmetric Multiprocessing and
-- 
2.20.1


  reply	other threads:[~2021-04-18 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 16:10 [PATCH 1/2] docs/zh_CN: Add translation zh_CN/kernel-hacking/locking.rst Wu XiangCheng
2021-04-18 16:11 ` Wu XiangCheng [this message]
2021-04-19  3:32 ` teng sterling
2021-04-19  6:04   ` Wu X.C.
2021-04-19 11:57   ` teng sterling
2021-04-19 13:00     ` 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=6a15b17d46f5db190fb10afc57ea59132b33c701.1618761749.git.bobwxc@email.cn \
    --to=bobwxc@email.cn \
    --cc=corbet@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.