From: Jonathan Corbet <corbet@lwn.net>
To: Miles Krause <mileskrause5200@gmail.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Miles Krause <mileskrause5200@gmail.com>
Subject: Re: [PATCH] Documentation/scheduler: Fix duplicated word in sched-deadline
Date: Sun, 03 May 2026 08:51:48 -0600 [thread overview]
Message-ID: <87se88czqz.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260429222435.2041-1-mileskrause5200@gmail.com>
Miles Krause <mileskrause5200@gmail.com> writes:
> The SCHED_DEADLINE documentation has a duplicated the in the CPU
> affinity section.
>
> Remove the extra word.
>
> Signed-off-by: Miles Krause <mileskrause5200@gmail.com>
> ---
> Documentation/scheduler/sched-deadline.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-deadline.rst b/Documentation/scheduler/sched-deadline.rst
> index 3ad93cd7b59a..9019b66f6a5b 100644
> --- a/Documentation/scheduler/sched-deadline.rst
> +++ b/Documentation/scheduler/sched-deadline.rst
> @@ -685,7 +685,7 @@ Deadline Task Scheduling
>
> Deadline tasks cannot have a cpu affinity mask smaller than the root domain they
> are created on. So, using ``sched_setaffinity(2)`` won't work. Instead, the
> - the deadline task should be created in a restricted root domain. This can be
> + deadline task should be created in a restricted root domain. This can be
> done using the cpuset controller of either cgroup v1 (deprecated) or cgroup v2.
Applied, thanks,
jon
prev parent reply other threads:[~2026-05-03 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 22:24 [PATCH] Documentation/scheduler: Fix duplicated word in sched-deadline Miles Krause
2026-05-03 14:51 ` 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=87se88czqz.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mileskrause5200@gmail.com \
/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