From: "tip-bot2 for Slark Xiao" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Slark Xiao <slark_xiao@163.com>, Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/urgent] perf/core: Fix ';;' typo
Date: Thu, 04 Aug 2022 09:09:51 -0000 [thread overview]
Message-ID: <165960419118.15455.15553677582415200869.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220720091220.14200-1-slark_xiao@163.com>
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 99643bab36b642be10bf09cd3285c37c9e5b597f
Gitweb: https://git.kernel.org/tip/99643bab36b642be10bf09cd3285c37c9e5b597f
Author: Slark Xiao <slark_xiao@163.com>
AuthorDate: Wed, 20 Jul 2022 17:12:20 +08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Thu, 04 Aug 2022 11:01:30 +02:00
perf/core: Fix ';;' typo
Remove double ';;'.
Signed-off-by: Slark Xiao <slark_xiao@163.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20220720091220.14200-1-slark_xiao@163.com
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index c9d32d4..bd23f3e 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -4457,7 +4457,7 @@ int perf_event_read_local(struct perf_event *event, u64 *value,
*value = local64_read(&event->count);
if (enabled || running) {
- u64 __enabled, __running, __now;;
+ u64 __enabled, __running, __now;
calc_timer_values(event, &__now, &__enabled, &__running);
if (enabled)
prev parent reply other threads:[~2022-08-04 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 9:12 [PATCH] perf/core: Fix typo Slark Xiao
2022-08-04 9:09 ` tip-bot2 for Slark Xiao [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=165960419118.15455.15553677582415200869.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=slark_xiao@163.com \
--cc=x86@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).