From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Sachin Saxena <sachin.saxena@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [PATCH] rawdev: fix build with clang 21
Date: Wed, 5 Nov 2025 08:16:46 +0100 [thread overview]
Message-ID: <CAJFAV8x7_9AVY6--gdUauNJ=swQZ6AWdd9eWqCq12UF3MybhLA@mail.gmail.com> (raw)
In-Reply-To: <20251104130808.2692053-1-david.marchand@redhat.com>
On Tue, 4 Nov 2025 at 14:08, David Marchand <david.marchand@redhat.com> wrote:
>
> Fix 16-bits formatting issues reported by clang 21 on Fedora 43:
>
> ../lib/rawdev/rte_rawdev.c:429:41: error: format specifies type
> 'unsigned char' but the argument has type 'uint16_t'
> (aka 'unsigned short') [-Werror,-Wformat]
> 429 | RTE_RDEV_DEBUG("Start dev_id=%" PRIu8, dev_id);
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
>
> ../lib/rawdev/rte_rawdev.c:435:9: error: format specifies type
> 'unsigned char' but the argument has type 'uint16_t'
> (aka 'unsigned short') [-Werror,-Wformat]
> 434 | RTE_RDEV_ERR("Device with dev_id=%" PRIu8 "already started",
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 435 | dev_id);
> | ^~~~~~~
>
> ../lib/rawdev/rte_rawdev.c:457:40: error: format specifies type
> 'unsigned char' but the argument has type 'uint16_t'
> (aka 'unsigned short') [-Werror,-Wformat]
> 457 | RTE_RDEV_DEBUG("Stop dev_id=%" PRIu8, dev_id);
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
>
> ../lib/rawdev/rte_rawdev.c:464:4: error: format specifies type
> 'unsigned char' but the argument has type 'uint16_t'
> (aka 'unsigned short') [-Werror,-Wformat]
> 463 | RTE_RDEV_ERR("Device with dev_id=%" PRIu8 "already stopped",
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 464 | dev_id);
> | ^~~~~~~
>
> Fixes: c88b3f2558ed ("rawdev: introduce raw device library")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2025-11-05 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 13:08 David Marchand
2025-11-05 7:16 ` David Marchand [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='CAJFAV8x7_9AVY6--gdUauNJ=swQZ6AWdd9eWqCq12UF3MybhLA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@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 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).