From: Shreenidhi Shedi <yesshedi@gmail.com>
To: gregkh@linuxfoundation.org, acme@kernel.org, linux@treblig.org,
mikhail.v.gavrilov@gmail.com
Cc: yesshedi@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH v1 00/18] Backport fixes for -Wdiscarded-qualifiers and -Wnonnull with newer glibc
Date: Sat, 9 May 2026 23:05:32 +0530 [thread overview]
Message-ID: <20260509173550.10926-1-yesshedi@gmail.com> (raw)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Hi all,
This patch series backports a number of patches from master to 6.1.y
to fix `-Wdiscarded-qualifiers` and `-Wnonnull` build issues with
newer glibc versions.
Arnaldo Carvalho de Melo (12):
perf diff: Constify strchr() return variables
perf test bpf: Address error about non-null argument for epoll_pwait
2nd arg
perf trace: Deal with compiler const checks
perf tools: Use const for variables receiving str{str,r?chr}() returns
perf strlist: Don't write to const memory
perf metricgroup: Constify variables storing the result of strchr() on
const tables
perf session: Don't write to memory pointed to a const pointer
perf trace-event: Constify variables storing the result of strchr() on
const tables
perf units: Constify variables storing the result of strchr() on const
tables
perf time-utils: Constify variables storing the result of strchr() on
const tables
perf demangle-java: Constify variables storing the result of strchr()
on const tables
perf bpf-event: Constify variables storing the result of strchr() on
const tables
Dr. David Alan Gilbert (1):
perf tools: Remove unused color_fwrite_lines
Mikhail Gavrilov (1):
libbpf: Fix -Wdiscarded-qualifiers under C23
Shreenidhi Shedi (4):
perf list: Fix -Wdiscarded-qualifiers under C23
perf parse-events: Fix -Wdiscarded-qualifiers under C23
perf bpf: Fix -Wdiscarded-qualifiers under C23
perf parse-events:: Fix -Wdiscarded-qualifiers under C23
tools/lib/bpf/libbpf.c | 2 +-
tools/perf/builtin-diff.c | 12 +++++-------
tools/perf/builtin-list.c | 3 ++-
tools/perf/builtin-trace.c | 2 +-
tools/perf/jvmti/libjvmti.c | 2 +-
tools/perf/tests/bpf.c | 3 ++-
tools/perf/util/bpf-event.c | 3 ++-
tools/perf/util/bpf-loader.c | 2 +-
tools/perf/util/color.c | 28 ----------------------------
tools/perf/util/color.h | 1 -
tools/perf/util/demangle-java.c | 2 +-
tools/perf/util/evlist.c | 3 ++-
tools/perf/util/metricgroup.c | 3 +--
tools/perf/util/parse-events.c | 2 +-
tools/perf/util/print-events.c | 4 ++--
tools/perf/util/session.c | 6 +++---
tools/perf/util/strlist.c | 12 ++++++++----
tools/perf/util/time-utils.c | 4 ++--
tools/perf/util/trace-event-info.c | 2 +-
tools/perf/util/units.c | 2 +-
20 files changed, 37 insertions(+), 61 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-09 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 17:35 Shreenidhi Shedi [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-09 17:35 [PATCH v1 00/18] Backport fixes for -Wdiscarded-qualifiers and -Wnonnull with newer glibc Shreenidhi Shedi
2026-05-10 16:25 ` Greg KH
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=20260509173550.10926-1-yesshedi@gmail.com \
--to=yesshedi@gmail.com \
--cc=acme@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mikhail.v.gavrilov@gmail.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