From: Ian Rogers <irogers@google.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH perf-next 0/4] glibc str functions const return fixes
Date: Thu, 11 Dec 2025 21:23:33 -0800 [thread overview]
Message-ID: <CAP-5=fUaGbbd4z6RcdsV86w=Tta6-s4GikuwJZjFDFjnTQzjwA@mail.gmail.com> (raw)
In-Reply-To: <20251211221756.96294-1-acme@kernel.org>
On Thu, Dec 11, 2025 at 2:18 PM Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
>
> Hi,
>
> While building with Fedora 44 I noticed so interesting warnings
> about touching const memory, fix some of them in this series,
>
> - Arnaldo
For the series:
Reviewed-by: Ian Rogers <irogers@google.com>
Thanks,
Ian
>
> Arnaldo Carvalho de Melo (4):
> perf list: Remove unused 'sep' variable
> perf diff: Constify strchr() return variables
> perf tools: Use const for variables receiving str{str,r?chr}() returns
> perf trace: Don't change const char strings
>
> tools/perf/builtin-diff.c | 12 +++++-------
> tools/perf/builtin-list.c | 4 ++--
> tools/perf/builtin-trace.c | 11 +++++++----
> tools/perf/jvmti/libjvmti.c | 2 +-
> tools/perf/tests/parse-events.c | 4 ++--
> tools/perf/util/evlist.c | 3 ++-
> 6 files changed, 19 insertions(+), 17 deletions(-)
>
> --
> 2.52.0
>
next prev parent reply other threads:[~2025-12-12 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 22:17 [PATCH perf-next 0/4] glibc str functions const return fixes Arnaldo Carvalho de Melo
2025-12-11 22:17 ` [PATCH 1/4] perf list: Remove unused 'sep' variable Arnaldo Carvalho de Melo
2025-12-11 22:17 ` [PATCH 2/4] perf diff: Constify strchr() return variables Arnaldo Carvalho de Melo
2025-12-11 22:17 ` [PATCH 3/4] perf tools: Use const for variables receiving str{str,r?chr}() returns Arnaldo Carvalho de Melo
2025-12-11 22:17 ` [PATCH 4/4] perf trace: Don't change const char strings Arnaldo Carvalho de Melo
2025-12-12 5:23 ` Ian Rogers [this message]
2025-12-16 18:23 ` [PATCH perf-next 0/4] glibc str functions const return fixes 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='CAP-5=fUaGbbd4z6RcdsV86w=Tta6-s4GikuwJZjFDFjnTQzjwA@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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).