From: Derek Foreman <derek.foreman@collabora.com>
To: 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>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>
Cc: kernel@collabora.com, Derek Foreman <derek.foreman@collabora.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] perf data: Fix coding style
Date: Fri, 28 Nov 2025 15:50:18 -0600 [thread overview]
Message-ID: <20251128215020.184466-2-derek.foreman@collabora.com> (raw)
In-Reply-To: <20251128215020.184466-1-derek.foreman@collabora.com>
Adjust some oddly indented fprintf() calls.
Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
---
tools/perf/util/data-convert-bt.c | 6 ++----
tools/perf/util/data-convert-json.c | 9 ++++-----
2 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/tools/perf/util/data-convert-bt.c b/tools/perf/util/data-convert-bt.c
index 0bcbc0e309e0..a22e9049ff30 100644
--- a/tools/perf/util/data-convert-bt.c
+++ b/tools/perf/util/data-convert-bt.c
@@ -1693,12 +1693,10 @@ int bt_convert__perf2ctf(const char *input, const char *path,
else
pr_err("Error during conversion.\n");
- fprintf(stderr,
- "[ perf data convert: Converted '%s' into CTF data '%s' ]\n",
+ fprintf(stderr, "[ perf data convert: Converted '%s' into CTF data '%s' ]\n",
data.path, path);
- fprintf(stderr,
- "[ perf data convert: Converted and wrote %.3f MB (%" PRIu64 " samples",
+ fprintf(stderr, "[ perf data convert: Converted and wrote %.3f MB (%" PRIu64 " samples",
(double) c.events_size / 1024.0 / 1024.0,
c.events_count);
diff --git a/tools/perf/util/data-convert-json.c b/tools/perf/util/data-convert-json.c
index 787039967916..eefa3a94c813 100644
--- a/tools/perf/util/data-convert-json.c
+++ b/tools/perf/util/data-convert-json.c
@@ -427,13 +427,12 @@ int bt_convert__perf2json(const char *input_name, const char *output_name,
output_json_format(c.out, false, 0, "}");
fputc('\n', c.out);
- fprintf(stderr,
- "[ perf data convert: Converted '%s' into JSON data '%s' ]\n",
- data.path, output_name);
+ fprintf(stderr, "[ perf data convert: Converted '%s' into JSON data '%s' ]\n",
+ data.path, output_name);
fprintf(stderr,
- "[ perf data convert: Converted and wrote %.3f MB (%" PRIu64 " samples) ]\n",
- (ftell(c.out)) / 1024.0 / 1024.0, c.events_count);
+ "[ perf data convert: Converted and wrote %.3f MB (%" PRIu64 " samples) ]\n",
+ (ftell(c.out)) / 1024.0 / 1024.0, c.events_count);
if (c.skipped) {
fprintf(stderr, "[ perf data convert: Skipped %" PRIu64 " samples ]\n",
--
2.47.3
prev parent reply other threads:[~2025-11-28 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 21:50 [PATCH v2 1/2] perf data: Allow filtering conversion by time range Derek Foreman
2025-11-28 21:50 ` Derek Foreman [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=20251128215020.184466-2-derek.foreman@collabora.com \
--to=derek.foreman@collabora.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kernel@collabora.com \
--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).