From: Jonathan Corbet <corbet@lwn.net>
To: Chun-Hung Tseng <henrybear327@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Chun-Hung Tseng <henrybear327@gmail.com>
Subject: Re: [PATCH v4] Documentation: scheduler: fixed 2 typos in sched-nice-design.rst
Date: Mon, 17 May 2021 12:43:45 -0600 [thread overview]
Message-ID: <87pmxp19r2.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210516105955.120651-1-henrybear327@gmail.com>
Chun-Hung Tseng <henrybear327@gmail.com> writes:
> This patch fixed 2 spelling errors in the documentation.
Next time, word this in the imperative form ("Fix two spelling
errors...") and leave out "this patch". Meanwhile...
> Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
> ---
> Documentation/scheduler/sched-nice-design.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-nice-design.rst b/Documentation/scheduler/sched-nice-design.rst
> index 0571f1b47e64..889bf2b737dc 100644
> --- a/Documentation/scheduler/sched-nice-design.rst
> +++ b/Documentation/scheduler/sched-nice-design.rst
> @@ -60,7 +60,7 @@ within the constraints of HZ and jiffies and their nasty design level
> coupling to timeslices and granularity it was not really viable.
>
> The second (less frequent but still periodically occurring) complaint
> -about Linux's nice level support was its assymetry around the origo
> +about Linux's nice level support was its asymmetry around the origin
> (which you can see demonstrated in the picture above), or more
Applied, thanks.
jon
prev parent reply other threads:[~2021-05-17 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 10:59 [PATCH v4] Documentation: scheduler: fixed 2 typos in sched-nice-design.rst Chun-Hung Tseng
2021-05-17 18:43 ` 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=87pmxp19r2.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=henrybear327@gmail.com \
--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 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).