From: Jonathan Corbet <corbet@lwn.net>
To: Colin King <colin.king@canonical.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>,
linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc/admin-guide: fix spelling mistake: "perfomance" -> "performance"
Date: Thu, 11 Feb 2021 09:39:12 -0700 [thread overview]
Message-ID: <875z2yr233.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210210115624.53551-1-colin.king@canonical.com>
Colin King <colin.king@canonical.com> writes:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in the perf-security documentation. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> Documentation/admin-guide/perf-security.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/perf-security.rst b/Documentation/admin-guide/perf-security.rst
> index 904e4eb37f99..34aa334320ca 100644
> --- a/Documentation/admin-guide/perf-security.rst
> +++ b/Documentation/admin-guide/perf-security.rst
> @@ -72,7 +72,7 @@ monitoring and observability operations, thus, bypass *scope* permissions
> checks in the kernel. CAP_PERFMON implements the principle of least
> privilege [13]_ (POSIX 1003.1e: 2.2.2.39) for performance monitoring and
> observability operations in the kernel and provides a secure approach to
> -perfomance monitoring and observability in the system.
> +performance monitoring and observability in the system.
Applied, thanks.
jon
prev parent reply other threads:[~2021-02-11 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 11:56 [PATCH] doc/admin-guide: fix spelling mistake: "perfomance" -> "performance" Colin King
2021-02-11 16:39 ` 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=875z2yr233.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=acme@redhat.com \
--cc=alexey.budankov@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--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).