mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: peterz@infradead.org, mingo@redhat.com, namhyung@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	liujing <liujing@cmss.chinamobile.com>
Subject: Re: [PATCH] perf bench messaging: Fix the formatting issue when printing.
Date: Wed, 16 Sep 2026 10:55:21 -0300	[thread overview]
Message-ID: <aqqfyX9nkOrVqwUb@x2> (raw)
In-Reply-To: <20260915221122.2174928-1-irogers@google.com>

On Tue, Sep 15, 2026 at 03:11:22PM -0700, Ian Rogers wrote:
> From: liujing <liujing@cmss.chinamobile.com>
> 
> The unsigned int type should use the %u format specifier when
> printing with printf or related functions.
> 
> Signed-off-by: liujing <liujing@cmss.chinamobile.com>
> Reviewed-by: Ian Rogeres <irogers@google.com>

s/Rogeres/Rogers/g

Applied,

- Arnaldo

> ---
>  tools/perf/bench/sched-messaging.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/bench/sched-messaging.c b/tools/perf/bench/sched-messaging.c
> index 4fb6657fc826..c5c9a7a1d7db 100644
> --- a/tools/perf/bench/sched-messaging.c
> +++ b/tools/perf/bench/sched-messaging.c
> @@ -338,9 +338,9 @@ int bench_sched_messaging(int argc, const char **argv)
>  
>  	switch (bench_format) {
>  	case BENCH_FORMAT_DEFAULT:
> -		printf("# %d sender and receiver %s per group\n",
> +		printf("# %u sender and receiver %s per group\n",
>  		       num_fds, thread_mode ? "threads" : "processes");
> -		printf("# %d groups == %d %s run\n\n",
> +		printf("# %u groups == %u %s run\n\n",
>  		       num_groups, num_groups * 2 * num_fds,
>  		       thread_mode ? "threads" : "processes");
>  		printf(" %14s: %lu.%03lu [sec]\n", "Total time",
> -- 
> 2.55.0.1032.g73a4cd73de-goog

      reply	other threads:[~2026-09-16 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22  9:17 liujing
2026-09-15 22:11 ` Ian Rogers
2026-09-16 13:55   ` Arnaldo Carvalho de Melo [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=aqqfyX9nkOrVqwUb@x2 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=liujing@cmss.chinamobile.com \
    --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

all inboxes | Powered by JetHome®