From: tip-bot for Colin Ian King <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: peterz@infradead.org, jolsa@redhat.com,
torvalds@linux-foundation.org,
alexander.shishkin@linux.intel.com, colin.king@canonical.com,
tglx@linutronix.de, mingo@kernel.org, acme@kernel.org,
namhyung@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: [tip:perf/urgent] perf/headers: Fix spelling mistake in <linux/perf_event.h> comment, EACCESS -> EACCES
Date: Mon, 29 Oct 2018 04:35:45 -0700 [thread overview]
Message-ID: <tip-1df02354b42f3f4504b6287c54a8cfbe1533719f@git.kernel.org> (raw)
In-Reply-To: <20181026175839.4565-1-colin.king@canonical.com>
Commit-ID: 1df02354b42f3f4504b6287c54a8cfbe1533719f
Gitweb: https://git.kernel.org/tip/1df02354b42f3f4504b6287c54a8cfbe1533719f
Author: Colin Ian King <colin.king@canonical.com>
AuthorDate: Fri, 26 Oct 2018 18:58:39 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Mon, 29 Oct 2018 07:21:07 +0100
perf/headers: Fix spelling mistake in <linux/perf_event.h> comment, EACCESS -> EACCES
Trivial fix to a spelling mistake of the error access name 'EACCESS',
rename to EACCES.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel-janitors@vger.kernel.org
Link: http://lkml.kernel.org/r/20181026175839.4565-1-colin.king@canonical.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
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 53c500f0ca79..57b07c9ddeb4 100644
--- a/include/linux/perf_event.h
+++ b/include/linux/perf_event.h
@@ -288,7 +288,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
*
next prev parent reply other threads:[~2018-10-29 11:36 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-bot for Colin Ian King [this message]
2018-10-29 12:28 ` Arnaldo Carvalho de Melo
2018-10-29 12:33 ` Colin Ian King
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=tip-1df02354b42f3f4504b6287c54a8cfbe1533719f@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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