public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 0/3] kernel-hacking documentation cleanup
Date: Tue, 23 Dec 2025 10:52:50 +0700	[thread overview]
Message-ID: <20251223035254.22894-1-bagasdotme@gmail.com> (raw)

Hi,

Here are additional docs cleanup for kernel-hacking documentation. It
is based on Thorsten's :c:func: annotation removal [1].

Enjoy!

[1]: https://lore.kernel.org/linux-doc/20251222232506.2615-2-thorsten.blum@linux.dev/

Bagas Sanjaya (3):
  Documentation: kernel-hacking: Remove current macro annotation
  Documentation: kernel-hacking: Do not italicize EXPORT_SYMBOL{,_GPL}()
    references
  Documentation: kernel-hacking: Convert internal links

 Documentation/kernel-hacking/hacking.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

-- 
An old man doll... just what I always wanted! - Clara


             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 Bagas Sanjaya [this message]
2025-12-23  3:52 ` [PATCH 1/3] Documentation: kernel-hacking: Remove current macro annotation Bagas Sanjaya
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-1-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