From: Thorsten Blum <thorsten.blum@linux.dev>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kernel-hacking: Remove comma
Date: Fri, 19 Dec 2025 22:40:56 +0100 [thread overview]
Message-ID: <7BF3E93E-DA92-4FC0-B352-C3766A97B3CD@linux.dev> (raw)
In-Reply-To: <87pl8akvkv.fsf@trenco.lwn.net>
On 19. Dec 2025, at 22:31, Jonathan Corbet wrote:
> Thorsten Blum <thorsten.blum@linux.dev> writes:
>> The comma is wrong, remove it.
>>
>> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>> ---
>> Documentation/kernel-hacking/hacking.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
>> index 0042776a9e17..06fcb7c662d3 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 :c:func:`schedule()`.
>
> That's a fine change, but can I prevail upon you to get rid of the
> usless :c:func: annotation while you're playing with that line?
So just `schedule()`?
:c:func: is used very often in the same file - maybe we should remove
them all in a separate patch? I'm fine either way.
Thanks,
Thorsten
next prev parent reply other threads:[~2025-12-19 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 17:18 [PATCH] Documentation: kernel-hacking: Remove comma Thorsten Blum
2025-12-19 17:55 ` Randy Dunlap
2025-12-19 21:31 ` Jonathan Corbet
2025-12-19 21:40 ` Thorsten Blum [this message]
2025-12-19 21:58 ` Jonathan Corbet
2025-12-22 21:41 ` 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=7BF3E93E-DA92-4FC0-B352-C3766A97B3CD@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.