linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Andrew Kreimer <algonell@gmail.com>,
	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>, Ian Rogers <irogers@google.com>,
	Liang Kan <kan.liang@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix typos Muliplier -> Multiplier
Date: Mon, 11 Nov 2024 08:17:29 +0200	[thread overview]
Message-ID: <c1592c50-e903-4ee5-a560-530792fcbae7@intel.com> (raw)
In-Reply-To: <20241108134728.25515-1-algonell@gmail.com>

On 8/11/24 15:47, Andrew Kreimer wrote:
> There are some typos in fprintf messages.
> Fix them via codespell.
> 
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>

Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>

> ---
>  tools/perf/util/intel-bts.c | 2 +-
>  tools/perf/util/intel-pt.c  | 2 +-
>  tools/perf/util/tsc.c       | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/util/intel-bts.c b/tools/perf/util/intel-bts.c
> index 3ea82d5e8d2e..a7c589fecb98 100644
> --- a/tools/perf/util/intel-bts.c
> +++ b/tools/perf/util/intel-bts.c
> @@ -808,7 +808,7 @@ static int intel_bts_synth_events(struct intel_bts *bts,
>  static const char * const intel_bts_info_fmts[] = {
>  	[INTEL_BTS_PMU_TYPE]		= "  PMU Type           %"PRId64"\n",
>  	[INTEL_BTS_TIME_SHIFT]		= "  Time Shift         %"PRIu64"\n",
> -	[INTEL_BTS_TIME_MULT]		= "  Time Muliplier     %"PRIu64"\n",
> +	[INTEL_BTS_TIME_MULT]		= "  Time Multiplier    %"PRIu64"\n",
>  	[INTEL_BTS_TIME_ZERO]		= "  Time Zero          %"PRIu64"\n",
>  	[INTEL_BTS_CAP_USER_TIME_ZERO]	= "  Cap Time Zero      %"PRId64"\n",
>  	[INTEL_BTS_SNAPSHOT_MODE]	= "  Snapshot mode      %"PRId64"\n",
> diff --git a/tools/perf/util/intel-pt.c b/tools/perf/util/intel-pt.c
> index 3fe67bf652b6..30be6dfe09eb 100644
> --- a/tools/perf/util/intel-pt.c
> +++ b/tools/perf/util/intel-pt.c
> @@ -4110,7 +4110,7 @@ static int intel_pt_parse_vm_tm_corr_args(struct intel_pt *pt)
>  static const char * const intel_pt_info_fmts[] = {
>  	[INTEL_PT_PMU_TYPE]		= "  PMU Type            %"PRId64"\n",
>  	[INTEL_PT_TIME_SHIFT]		= "  Time Shift          %"PRIu64"\n",
> -	[INTEL_PT_TIME_MULT]		= "  Time Muliplier      %"PRIu64"\n",
> +	[INTEL_PT_TIME_MULT]		= "  Time Multiplier     %"PRIu64"\n",
>  	[INTEL_PT_TIME_ZERO]		= "  Time Zero           %"PRIu64"\n",
>  	[INTEL_PT_CAP_USER_TIME_ZERO]	= "  Cap Time Zero       %"PRId64"\n",
>  	[INTEL_PT_TSC_BIT]		= "  TSC bit             %#"PRIx64"\n",
> diff --git a/tools/perf/util/tsc.c b/tools/perf/util/tsc.c
> index 2e33a20e1e1b..511a517ce613 100644
> --- a/tools/perf/util/tsc.c
> +++ b/tools/perf/util/tsc.c
> @@ -119,7 +119,7 @@ size_t perf_event__fprintf_time_conv(union perf_event *event, FILE *fp)
>  	size_t ret;
>  
>  	ret  = fprintf(fp, "\n... Time Shift      %" PRI_lu64 "\n", tc->time_shift);
> -	ret += fprintf(fp, "... Time Muliplier  %" PRI_lu64 "\n", tc->time_mult);
> +	ret += fprintf(fp, "... Time Multiplier %" PRI_lu64 "\n", tc->time_mult);
>  	ret += fprintf(fp, "... Time Zero       %" PRI_lu64 "\n", tc->time_zero);
>  
>  	/*


  reply	other threads:[~2024-11-11  6:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 13:47 [PATCH] perf tools: Fix typos Muliplier -> Multiplier Andrew Kreimer
2024-11-11  6:17 ` Adrian Hunter [this message]
2024-11-11 17:29   ` Arnaldo Carvalho de Melo

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=c1592c50-e903-4ee5-a560-530792fcbae7@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=algonell@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).