From: fengchengwen <fengchengwen@huawei.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Huisong Li <lihuisong@huawei.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>
Subject: Re: [PATCH 2/7] bus/uacce: fix const pointer in device matching
Date: Sat, 29 Nov 2025 08:32:30 +0800 [thread overview]
Message-ID: <d4a367ac-8082-4583-96d8-a2db3774f9b6@huawei.com> (raw)
In-Reply-To: <20251128135616.2662164-3-david.marchand@redhat.com>
Reviewed-by: Chengwen Feng <fengchengwen@huawei.com>
On 11/28/2025 9:56 PM, David Marchand wrote:
> With latest glibc (Fedora Rawhide):
> ../drivers/bus/uacce/uacce.c: In function 'uacce_match':
> ../drivers/bus/uacce/uacce.c:346:21: warning: assignment discards
> 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
> 346 | map = strstr(dev->algs, id_table->dev_alg);
> | ^
>
> Fixes: 62b906cf06ba ("bus/uacce: introduce UACCE bus")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
next prev parent reply other threads:[~2025-11-29 0:32 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 [this message]
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 ` [PATCH 0/7] Fixes for Fedora Rawhide Thomas Monjalon
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=d4a367ac-8082-4583-96d8-a2db3774f9b6@huawei.com \
--to=fengchengwen@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=stable@dpdk.org \
--cc=zhangfei.gao@linaro.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).