linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kernel-hacking: Remove :c:func: annotations
Date: Mon, 22 Dec 2025 14:42:23 -0700	[thread overview]
Message-ID: <87wm2e19ds.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251220125233.76312-2-thorsten.blum@linux.dev>

Thorsten Blum <thorsten.blum@linux.dev> writes:

> Remove the useless :c:func: annotations.
>
> Suggested-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> Only applies after applying https://lore.kernel.org/lkml/20251219171827.44015-2-thorsten.blum@linux.dev/
> ---
>  Documentation/kernel-hacking/hacking.rst | 169 +++++++++++------------
>  1 file changed, 84 insertions(+), 85 deletions(-)
>
> diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
> index 06fcb7c662d3..8593ef3b8e6c 100644
> --- a/Documentation/kernel-hacking/hacking.rst
> +++ b/Documentation/kernel-hacking/hacking.rst
> @@ -49,7 +49,7 @@ User Context
>  
>  User context is when you are coming in from a system call or other trap:
>  like userspace, you can be preempted by more important tasks and by
> -interrupts. You can sleep by calling :c:func:`schedule()`.
> +interrupts. You can sleep by calling `schedule()`.

Almost ... the `backticks` are part of the :c:func: markup and need to
go as well.

Thanks,

jon

      reply	other threads:[~2025-12-22 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20 12:52 [PATCH] Documentation: kernel-hacking: Remove :c:func: annotations Thorsten Blum
2025-12-22 21:42 ` Jonathan Corbet [this message]

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=87wm2e19ds.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).