Received-SPF: pass (google.com: domain of linux-kernel+bounces-192699-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <669d0fcf-5afa-45c5-a836-eccad0884d33@arm.com>
Date: Tue, 28 May 2024 16:55:57 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v1] perf docs: Fix typos
To: Ian Rogers <irogers@google.com>
References: <20240521223555.858859-1-irogers@google.com>
Content-Language: en-US
Cc: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>,
 Arnaldo Carvalho de Melo <acme@kernel.org>,
 Namhyung Kim <namhyung@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
 Alexander Shishkin <alexander.shishkin@linux.intel.com>,
 Jiri Olsa <jolsa@kernel.org>, Adrian Hunter <adrian.hunter@intel.com>,
 Kan Liang <kan.liang@linux.intel.com>, Changbin Du <changbin.du@huawei.com>,
 linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
From: James Clark <james.clark@arm.com>
In-Reply-To: <20240521223555.858859-1-irogers@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


On 21/05/2024 23:35, Ian Rogers wrote:
> Assorted typo fixes.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>

Reviewed-by: James Clark <james.clark@arm.com>

> ---
>  tools/perf/Documentation/perf-kwork.txt  | 4 ++--
>  tools/perf/Documentation/perf-mem.txt    | 2 +-
>  tools/perf/Documentation/perf-record.txt | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-kwork.txt b/tools/perf/Documentation/perf-kwork.txt
> index 109ace1d5e90..21e607669d78 100644
> --- a/tools/perf/Documentation/perf-kwork.txt
> +++ b/tools/perf/Documentation/perf-kwork.txt
> @@ -1,4 +1,4 @@
> -perf-kowrk(1)
> +perf-kwork(1)
>  =============
>  
>  NAME
> @@ -35,7 +35,7 @@ There are several variants of 'perf kwork':
>          perf kwork top
>          perf kwork top -b
>  
> -   By default it shows the individual work events such as irq, workqeueu,
> +   By default it shows the individual work events such as irq, workqueue,
>     including the run time and delay (time between raise and actually entry):
>  
>        Runtime start      Runtime end        Cpu     Kwork name                 Runtime     Delaytime
> diff --git a/tools/perf/Documentation/perf-mem.txt b/tools/perf/Documentation/perf-mem.txt
> index 19862572e3f2..47456b212e99 100644
> --- a/tools/perf/Documentation/perf-mem.txt
> +++ b/tools/perf/Documentation/perf-mem.txt
> @@ -21,7 +21,7 @@ and stores are sampled. Use the -t option to limit to loads or stores.
>  
>  Note that on Intel systems the memory latency reported is the use-latency,
>  not the pure load (or store latency). Use latency includes any pipeline
> -queueing delays in addition to the memory subsystem latency.
> +queuing delays in addition to the memory subsystem latency.
>  
>  On Arm64 this uses SPE to sample load and store operations, therefore hardware
>  and kernel support is required. See linkperf:perf-arm-spe[1] for a setup guide.
> diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
> index 6015fdd08fb6..77578c0a142a 100644
> --- a/tools/perf/Documentation/perf-record.txt
> +++ b/tools/perf/Documentation/perf-record.txt
> @@ -311,7 +311,7 @@ OPTIONS
>  	User can change the size by passing the size after comma like
>  	"--call-graph dwarf,4096".
>  
> -	When "fp" recording is used, perf tries to save stack enties
> +	When "fp" recording is used, perf tries to save stack entries
>  	up to the number specified in sysctl.kernel.perf_event_max_stack
>  	by default.  User can change the number by passing it after comma
>  	like "--call-graph fp,32".