From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
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>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 14/14] perf: fix repeated word in log message
Date: Fri, 25 Sep 2026 15:10:27 +0200 [thread overview]
Message-ID: <arZyw5HCRm5EzF3L@x2> (raw)
In-Reply-To: <20260907065843.34410-1-hemanth.selam@gmail.com>
On Mon, Sep 07, 2026 at 12:28:43PM +0530, Hemanth Selam wrote:
> Drop the word written twice, reported by checkpatch.pl as a possible
> repeated word.
>
> Only the message text changes, no code changes.
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
> tools/perf/util/synthetic-events.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/synthetic-events.c b/tools/perf/util/synthetic-events.c
> index 0c150193cca8..b9e5a5da5f6e 100644
> --- a/tools/perf/util/synthetic-events.c
> +++ b/tools/perf/util/synthetic-events.c
> @@ -2266,7 +2266,7 @@ int perf_event__synthesize_extra_attr(const struct perf_tool *tool, struct evlis
> if (has_scale(evsel)) {
> err = perf_event__synthesize_event_update_scale(tool, evsel, process);
> if (err < 0) {
> - pr_err("Couldn't synthesize evsel evsel.\n");
> + pr_err("Couldn't synthesize evsel.\n");
> return err;
> }
> }
prev parent reply other threads:[~2026-09-25 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:58 [PATCH 14/14] perf: fix repeated word in log message Hemanth Selam
2026-09-25 13:10 ` 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=arZyw5HCRm5EzF3L@x2 \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=hemanth.selam@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.