The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>,
	linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Suchit Karunakaran <suchitkarunakaran@gmail.com>
Subject: Re: [PATCH] docs: scheduler: fix spelling in sched-bwc documentation
Date: Fri, 21 Feb 2025 13:27:13 -0700	[thread overview]
Message-ID: <87eczrgi1q.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250219112254.28691-1-suchitkarunakaran@gmail.com>

Suchit Karunakaran <suchitkarunakaran@gmail.com> writes:

> Fix spelling of "interference" in the CFS bandwidth control documentation. 
> The word was misspelled as "interferenece".
>
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
> ---
>  Documentation/scheduler/sched-bwc.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst
> index 41ed2ceafc92..e881a945c188 100644
> --- a/Documentation/scheduler/sched-bwc.rst
> +++ b/Documentation/scheduler/sched-bwc.rst
> @@ -59,7 +59,7 @@ At the same time, we can say that the worst case deadline miss, will be
>  \Sum e_i; that is, there is a bounded tardiness (under the assumption
>  that x+e is indeed WCET).
>  
> -The interferenece when using burst is valued by the possibilities for
> +The interference when using burst is valued by the possibilities for
>  missing the deadline and the average WCET. Test results showed that when

Applied, thanks.

jon

      reply	other threads:[~2025-02-21 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 11:22 [PATCH] docs: scheduler: fix spelling in sched-bwc documentation Suchit Karunakaran
2025-02-21 20:27 ` 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=87eczrgi1q.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suchitkarunakaran@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