From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Thorsten Blum <thorsten.blum@linux.dev>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH 1/3] Documentation: kernel-hacking: Remove current macro annotation
Date: Tue, 23 Dec 2025 10:52:51 +0700 [thread overview]
Message-ID: <20251223035254.22894-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20251223035254.22894-1-bagasdotme@gmail.com>
Remove unneeded :c:macro: annotation of current macro.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/kernel-hacking/hacking.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
index bd5401b924427e..a5f7a1df7fb97d 100644
--- a/Documentation/kernel-hacking/hacking.rst
+++ b/Documentation/kernel-hacking/hacking.rst
@@ -345,8 +345,8 @@ routine.
Before inventing your own cache of often-used objects consider using a
slab cache in ``include/linux/slab.h``
-:c:macro:`current`
-------------------
+current
+-------
Defined in ``include/asm/current.h``
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-12-23 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 3:52 [PATCH 0/3] kernel-hacking documentation cleanup Bagas Sanjaya
2025-12-23 3:52 ` Bagas Sanjaya [this message]
2025-12-23 3:52 ` [PATCH 2/3] Documentation: kernel-hacking: Do not italicize EXPORT_SYMBOL{,_GPL}() references Bagas Sanjaya
2025-12-23 3:52 ` [PATCH 3/3] Documentation: kernel-hacking: Convert internal links Bagas Sanjaya
2026-01-06 22:09 ` [PATCH 0/3] kernel-hacking documentation cleanup Jonathan Corbet
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=20251223035254.22894-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=thorsten.blum@linux.dev \
/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