From: Ingo Molnar <mingo@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Jiri Kosina <trivial@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [trivial] perf: Spelling s/EACCESS/EACCES/
Date: Mon, 27 May 2019 16:12:01 +0200 [thread overview]
Message-ID: <20190527141201.GA1537@gmail.com> (raw)
In-Reply-To: <20190527122309.5840-1-geert+renesas@glider.be>
* Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> The correct spelling is EACCES:
>
> include/uapi/asm-generic/errno-base.h:#define EACCES 13 /* Permission denied */
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> include/linux/perf_event.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> index 0ab99c7b652d41b1..10569e25b5a9b656 100644
> --- a/include/linux/perf_event.h
> +++ b/include/linux/perf_event.h
> @@ -289,7 +289,7 @@ struct pmu {
> * -EBUSY -- @event is for this PMU but PMU temporarily unavailable
> * -EINVAL -- @event is for this PMU but @event is not valid
> * -EOPNOTSUPP -- @event is for this PMU, @event is valid, but not supported
> - * -EACCESS -- @event is for this PMU, @event is valid, but no privilidges
> + * -EACCES -- @event is for this PMU, @event is valid, but no privilidges
> *
> * 0 -- @event is for this PMU and valid
> *
Actually, -EACCES got typoed itself and survived due to historic reasons.
I think we can tolerate the 'typo' fixed in documentation, can we?
Also, the *far* bigger typo is, in the same line:
s/privilidges
/privileges
:-)
Thanks,
Ingo
next prev parent reply other threads:[~2019-05-27 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 12:23 [PATCH] [trivial] perf: Spelling s/EACCESS/EACCES/ Geert Uytterhoeven
2019-05-27 14:12 ` Ingo Molnar [this message]
2019-05-27 14:27 ` Geert Uytterhoeven
2019-05-27 15:15 ` Ingo Molnar
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=20190527141201.GA1537@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.