From: "tip-bot for Justin P. Mattock" <justinmattock@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, justinmattock@gmail.com,
hpa@zytor.com, mingo@redhat.com, tglx@linutronix.de,
gorcunov@gmail.com, mingo@elte.hu
Subject: [tip:perf/core] perf events, x86, P4: Fix typo in comment
Date: Mon, 25 Apr 2011 10:12:55 GMT [thread overview]
Message-ID: <tip-fa7b69475a6c192853949ba496dd9c37b497b548@git.kernel.org> (raw)
In-Reply-To: <1303492132-3004-1-git-send-email-justinmattock@gmail.com>
Commit-ID: fa7b69475a6c192853949ba496dd9c37b497b548
Gitweb: http://git.kernel.org/tip/fa7b69475a6c192853949ba496dd9c37b497b548
Author: Justin P. Mattock <justinmattock@gmail.com>
AuthorDate: Fri, 22 Apr 2011 10:08:52 -0700
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 24 Apr 2011 13:16:04 +0200
perf events, x86, P4: Fix typo in comment
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
Acked-by: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: trivial@kernel.org
Link: http://lkml.kernel.org/r/1303492132-3004-1-git-send-email-justinmattock@gmail.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/cpu/perf_event_p4.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event_p4.c b/arch/x86/kernel/cpu/perf_event_p4.c
index ae31e96..f4c1da2 100644
--- a/arch/x86/kernel/cpu/perf_event_p4.c
+++ b/arch/x86/kernel/cpu/perf_event_p4.c
@@ -1187,7 +1187,7 @@ static __init int p4_pmu_init(void)
{
unsigned int low, high;
- /* If we get stripped -- indexig fails */
+ /* If we get stripped -- indexing fails */
BUILD_BUG_ON(ARCH_P4_MAX_CCCR > X86_PMC_MAX_GENERIC);
rdmsr(MSR_IA32_MISC_ENABLE, low, high);
prev parent reply other threads:[~2011-04-25 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 17:08 [PATCH]arch:x86:kernel:cpu:perf_event_p4.c Typo: change indexig to indexing Justin P. Mattock
2011-04-22 17:12 ` Cyrill Gorcunov
2011-04-25 10:12 ` tip-bot for Justin P. Mattock [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-fa7b69475a6c192853949ba496dd9c37b497b548@git.kernel.org \
--to=justinmattock@gmail.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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