From: Phil Auld <pauld@redhat.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, stable@vger.kernel.org,
peterz@infradead.org, tglx@linutronix.de
Subject: Re: [PATCH] docs: sched: Update sched-rt-group Documentation For Gender Inclusiveness
Date: Fri, 6 May 2022 10:29:06 -0400 [thread overview]
Message-ID: <YnUwsnt52aB0sZi0@lorien.usersys.redhat.com> (raw)
In-Reply-To: <20220505021424.12656-1-joseph.salisbury@canonical.com>
On Wed, May 04, 2022 at 10:14:24PM -0400 Joseph Salisbury wrote:
> Document assumes root user is he:
> "assumes root knows what he is doing."
>
> Update documentation for inclusivness, since root is not limited by gender.
>
> Fixes: 60aa605dfce2 ("sched: rt: document the risk of small values in the bandwidth settings")
> Cc: stable@vger.kernel.org
> Signed-off-by: Joseph Salisbury <joseph.salisbury@canonical.com>
> ---
> Documentation/scheduler/sched-rt-group.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-rt-group.rst b/Documentation/scheduler/sched-rt-group.rst
> index 655a096ec8fb..e55fee6772c4 100644
> --- a/Documentation/scheduler/sched-rt-group.rst
> +++ b/Documentation/scheduler/sched-rt-group.rst
> @@ -19,7 +19,7 @@ Real-Time group scheduling
> ==========
>
> Fiddling with these settings can result in an unstable system, the knobs are
> - root only and assumes root knows what he is doing.
> + root only and assumes root knows what they are doing.
>
Now there's a singular vs plural problem.
"... assumes root users know ..." ?
Cheers,
Phil
> Most notable:
>
> --
> 2.34.1
>
--
next prev parent reply other threads:[~2022-05-06 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 2:14 [PATCH] docs: sched: Update sched-rt-group Documentation For Gender Inclusiveness Joseph Salisbury
2022-05-06 14:29 ` Phil Auld [this message]
2022-05-06 15:22 ` Joseph Salisbury
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=YnUwsnt52aB0sZi0@lorien.usersys.redhat.com \
--to=pauld@redhat.com \
--cc=corbet@lwn.net \
--cc=joseph.salisbury@canonical.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).