From: tip-bot for Su Yanjun <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
peterz@infradead.org, suyj.fnst@cn.fujitsu.com,
torvalds@linux-foundation.org, tglx@linutronix.de
Subject: [tip:perf/urgent] perf/x86: Fix typo in comment
Date: Mon, 19 Aug 2019 02:55:05 -0700 [thread overview]
Message-ID: <tip-77d760328ee015cf89460c52bfd5a6b0a09b7472@git.kernel.org> (raw)
In-Reply-To: <1565945001-4413-1-git-send-email-suyj.fnst@cn.fujitsu.com>
Commit-ID: 77d760328ee015cf89460c52bfd5a6b0a09b7472
Gitweb: https://git.kernel.org/tip/77d760328ee015cf89460c52bfd5a6b0a09b7472
Author: Su Yanjun <suyj.fnst@cn.fujitsu.com>
AuthorDate: Fri, 16 Aug 2019 16:43:21 +0800
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Mon, 19 Aug 2019 11:50:24 +0200
perf/x86: Fix typo in comment
No functional change.
Signed-off-by: Su Yanjun <suyj.fnst@cn.fujitsu.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1565945001-4413-1-git-send-email-suyj.fnst@cn.fujitsu.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 81b005e4c7d9..325959d19d9a 100644
--- a/arch/x86/events/core.c
+++ b/arch/x86/events/core.c
@@ -1236,7 +1236,7 @@ void x86_pmu_enable_event(struct perf_event *event)
* Add a single event to the PMU.
*
* The event is added to the group of enabled events
- * but only if it can be scehduled with existing events.
+ * but only if it can be scheduled with existing events.
*/
static int x86_pmu_add(struct perf_event *event, int flags)
{
prev parent reply other threads:[~2019-08-19 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 8:43 [PATCH] perf/x86: Fix typo in core.c Su Yanjun
2019-08-19 9:55 ` tip-bot for Su Yanjun [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=tip-77d760328ee015cf89460c52bfd5a6b0a09b7472@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=suyj.fnst@cn.fujitsu.com \
--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
Powered by JetHome