From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/7] Fixes for Fedora Rawhide
Date: Sat, 29 Nov 2025 20:02:26 +0100 [thread overview]
Message-ID: <4425601.mvXUDI8C0e@thomas> (raw)
In-Reply-To: <20251128135616.2662164-1-david.marchand@redhat.com>
28/11/2025 14:56, David Marchand:
> Similary to https://git.dpdk.org/dpdk/commit/?id=f4ef899bb3ae, we have
> many strstr/str*chr calls on const char * stored to non const pointers.
>
> This breaks build in Fedora Rawhide as a change in its glibc now
> triggers build warnings.
>
> Probably too late for 25.11, but sending in any case...
CI is green, it looks good to have in 25.11.
Applied, thanks.
prev parent reply other threads:[~2025-11-29 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 13:56 [PATCH 0/7] Fixes for Fedora Rawhide David Marchand
2025-11-28 13:56 ` [PATCH 1/7] bus/ifpga: fix const pointer in device name parsing David Marchand
2025-11-28 13:56 ` [PATCH 2/7] bus/uacce: fix const pointer in device matching David Marchand
2025-11-29 0:32 ` fengchengwen
2025-11-28 13:56 ` [PATCH 3/7] drivers: fix some const pointers in qat drivers David Marchand
2025-11-28 13:56 ` [PATCH 4/7] crypto/caam_jr: fix const pointer in UIO filename parsing David Marchand
2025-11-28 14:00 ` Hemant Agrawal
2025-11-28 13:56 ` [PATCH 5/7] net/enetfec: " David Marchand
2025-11-28 14:00 ` Hemant Agrawal
2025-11-28 13:56 ` [PATCH 6/7] net/memif: fix const pointer in socket check David Marchand
2025-11-28 13:56 ` [PATCH 7/7] app/procinfo: fix const pointer in collectd format David Marchand
2025-11-29 0:35 ` fengchengwen
2025-11-29 19:02 ` Thomas Monjalon [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=4425601.mvXUDI8C0e@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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.