linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for Ingo Molnar <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: jolsa@redhat.com, linux-kernel@vger.kernel.org, mingo@kernel.org,
	namhyung@kernel.org, hpa@zytor.com, peterz@infradead.org,
	tglx@linutronix.de, acme@redhat.com
Subject: [tip:perf/core] perf tools Documentation: Fix diverse typos
Date: Fri, 14 Dec 2018 12:41:20 -0800	[thread overview]
Message-ID: <tip-e1eebe9cc3d548a2fbbd97d978d133801a348cc3@git.kernel.org> (raw)
In-Reply-To: <20181203102200.GA104797@gmail.com>

Commit-ID:  e1eebe9cc3d548a2fbbd97d978d133801a348cc3
Gitweb:     https://git.kernel.org/tip/e1eebe9cc3d548a2fbbd97d978d133801a348cc3
Author:     Ingo Molnar <mingo@kernel.org>
AuthorDate: Mon, 3 Dec 2018 11:22:00 +0100
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 6 Dec 2018 14:12:31 -0300

perf tools Documentation: Fix diverse typos

Go over the tools/ files that are maintained in Arnaldo's tree and
fix common typos: half of them were in comments, the other half
in JSON files.

No change in functionality intended.

Committer notes:

This was split from a larger patch as there are code that is,
additionally, maintained outside the kernel tree, so to ease cherry
picking and/or backporting, split this into multiple patches.

In this particular case, it affects documentation, so may be interesting
to cherry pick as it is information that is presented to the user.

Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/20181203102200.GA104797@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/Documentation/perf-list.txt   | 2 +-
 tools/perf/Documentation/perf-report.txt | 2 +-
 tools/perf/Documentation/perf-stat.txt   | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt
index 667c14e56031..138fb6e94b3c 100644
--- a/tools/perf/Documentation/perf-list.txt
+++ b/tools/perf/Documentation/perf-list.txt
@@ -172,7 +172,7 @@ like cycles and instructions and some software events.
 Other PMUs and global measurements are normally root only.
 Some event qualifiers, such as "any", are also root only.
 
-This can be overriden by setting the kernel.perf_event_paranoid
+This can be overridden by setting the kernel.perf_event_paranoid
 sysctl to -1, which allows non root to use these events.
 
 For accessing trace point events perf needs to have read access to
diff --git a/tools/perf/Documentation/perf-report.txt b/tools/perf/Documentation/perf-report.txt
index ed2bf37ab132..1a27bfe05039 100644
--- a/tools/perf/Documentation/perf-report.txt
+++ b/tools/perf/Documentation/perf-report.txt
@@ -252,7 +252,7 @@ OPTIONS
 	          Usually more convenient to use --branch-history for this.
 
 	value can be:
-	- percent: diplay overhead percent (default)
+	- percent: display overhead percent (default)
 	- period: display event period
 	- count: display event count
 
diff --git a/tools/perf/Documentation/perf-stat.txt b/tools/perf/Documentation/perf-stat.txt
index b10a90b6a718..4bc2085e5197 100644
--- a/tools/perf/Documentation/perf-stat.txt
+++ b/tools/perf/Documentation/perf-stat.txt
@@ -50,7 +50,7 @@ report::
 	  /sys/bus/event_source/devices/<pmu>/format/*
 
 	Note that the last two syntaxes support prefix and glob matching in
-	the PMU name to simplify creation of events accross multiple instances
+	the PMU name to simplify creation of events across multiple instances
 	of the same type of PMU in large systems (e.g. memory controller PMUs).
 	Multiple PMU instances are typical for uncore PMUs, so the prefix
 	'uncore_' is also ignored when performing this match.
@@ -277,7 +277,7 @@ echo 0 > /proc/sys/kernel/nmi_watchdog
 for best results. Otherwise the bottlenecks may be inconsistent
 on workload with changing phases.
 
-This enables --metric-only, unless overriden with --no-metric-only.
+This enables --metric-only, unless overridden with --no-metric-only.
 
 To interpret the results it is usually needed to know on which
 CPUs the workload runs on. If needed the CPUs can be forced using

  parent reply	other threads:[~2018-12-14 20:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 10:22 [PATCH] tools: Fix diverse typos Ingo Molnar
2018-12-03 10:31 ` Peter Zijlstra
2018-12-03 10:52   ` Ingo Molnar
2018-12-04 17:16     ` Andi Kleen
2018-12-04 17:40       ` Arnaldo Carvalho de Melo
2018-12-04 13:41 ` Arnaldo Carvalho de Melo
2018-12-04 16:46   ` Steven Rostedt
2018-12-14 20:40 ` [tip:perf/core] perf vendor events intel: " tip-bot for Ingo Molnar
2018-12-14 20:40 ` [tip:perf/core] tools lib traceevent: Fix diverse typos in comments tip-bot for Ingo Molnar
2018-12-14 20:41 ` tip-bot for Ingo Molnar [this message]
2018-12-14 20:41 ` [tip:perf/core] perf bpf-loader: Fix debugging message typo tip-bot for Ingo Molnar
2018-12-14 20:42 ` [tip:perf/core] perf tools: Fix diverse comment typos tip-bot for Ingo Molnar
2018-12-14 20:43 ` [tip:perf/core] tools lib subcmd: Fix a few source code " tip-bot for Ingo Molnar
2018-12-18 14:07 ` [tip:perf/core] perf vendor events intel: Fix diverse typos tip-bot for Ingo Molnar
2018-12-18 14:07 ` [tip:perf/core] tools lib traceevent: Fix diverse typos in comments tip-bot for Ingo Molnar
2018-12-18 14:08 ` [tip:perf/core] perf tools Documentation: Fix diverse typos tip-bot for Ingo Molnar
2018-12-18 14:08 ` [tip:perf/core] perf bpf-loader: Fix debugging message typo tip-bot for Ingo Molnar
2018-12-18 14:09 ` [tip:perf/core] perf tools: Fix diverse comment typos tip-bot for Ingo Molnar
2018-12-18 14:09 ` [tip:perf/core] tools lib subcmd: Fix a few source code " tip-bot for 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-e1eebe9cc3d548a2fbbd97d978d133801a348cc3@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.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 \
    /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).