From: Colin Ian King <colin.king@canonical.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/perf: fix spelling mistake, EACCESS -> EACCES
Date: Mon, 29 Oct 2018 12:33:54 +0000 [thread overview]
Message-ID: <d7b6a544-183f-331b-c510-d78aefe27544@canonical.com> (raw)
In-Reply-To: <20181029122854.GB20813@kernel.org>
On 29/10/2018 12:28, Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 26, 2018 at 06:58:39PM +0100, Colin King escreveu:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> Trivial fix to a spelling mistake of the error access name EACCESS,
>> rename to EACCES
>
> Thanks, applied.
>
> And I also took the chance to fix another spelling mistake, on this same
> line:
>
> - * -EACCESS -- @event is for this PMU, @event is valid, but no privilidges
> + * -EACCES -- @event is for this PMU, @event is valid, but no privilidges
> ^
> ^
> ^
> ^
Nice find, I completely missed that :-)
>
> :-)
>
> - Arnaldo
>
next prev parent reply other threads:[~2018-10-29 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:58 [PATCH] drivers/perf: fix spelling mistake, EACCESS -> EACCES Colin King
2018-10-29 11:35 ` [tip:perf/urgent] perf/headers: Fix spelling mistake in <linux/perf_event.h> comment, " tip-bot for Colin Ian King
2018-10-29 12:28 ` [PATCH] drivers/perf: fix spelling mistake, " Arnaldo Carvalho de Melo
2018-10-29 12:33 ` Colin Ian King [this message]
2018-10-29 12:33 ` Arnaldo Carvalho de Melo
2018-10-29 12:36 ` Ingo Molnar
2018-10-29 13:20 ` Arnaldo Carvalho de Melo
2018-10-29 14:19 ` Ingo Molnar
2018-10-29 12:35 ` 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=d7b6a544-183f-331b-c510-d78aefe27544@canonical.com \
--to=colin.king@canonical.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).