From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Van Haaren Harry <harry.van.haaren@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Gao, DaxueX" <daxuex.gao@intel.com>
Subject: Re: [PATCH 00/11] Fixes for clang 15
Date: Mon, 21 Nov 2022 11:23:51 +0100 [thread overview]
Message-ID: <CAJFAV8y8QSAB7BFPQ4B0Cr2P8nEM8s=vZqDtP3wHC=ELtRY7hQ@mail.gmail.com> (raw)
In-Reply-To: <20221118085313.2118977-1-david.marchand@redhat.com>
On Fri, Nov 18, 2022 at 9:55 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> Fedora 37 has just been released with clang 15.
> The latter seems more picky wrt unused variable.
>
> Fixes have been tested in GHA with a simple patch I used in my own repo:
> https://github.com/david-marchand/dpdk/commit/82cd57ae5490
> https://github.com/david-marchand/dpdk/actions/runs/3495454457
>
> --
> David Marchand
>
> David Marchand (11):
> service: fix build with clang 15
> vhost: fix build with clang 15
> bus/dpaa: fix build with clang 15
> net/atlantic: fix build with clang 15
> net/dpaa2: fix build with clang 15
> net/ice: fix build with clang 15
> app/testpmd: fix build with clang 15
> app/testpmd: fix build with clang 15 in flow code
> test/efd: fix build with clang 15
> test/member: fix build with clang 15
> test/event: fix build with clang 15
>
> app/test-pmd/config.c | 14 --------------
> app/test-pmd/noisy_vnf.c | 2 +-
> app/test/test_efd_perf.c | 1 -
> app/test/test_event_timer_adapter.c | 2 --
> app/test/test_member.c | 1 -
> app/test/test_member_perf.c | 1 -
> drivers/bus/dpaa/base/qbman/bman.h | 4 +---
> drivers/net/atlantic/atl_rxtx.c | 5 ++---
> drivers/net/dpaa2/dpaa2_rxtx.c | 4 +---
> drivers/net/ice/ice_ddp_package.c | 3 ---
> lib/eal/common/rte_service.c | 2 --
> lib/vhost/virtio_net.c | 2 --
> 12 files changed, 5 insertions(+), 36 deletions(-)
Series applied for rc4, thanks.
--
David Marchand
prev parent reply other threads:[~2022-11-21 10:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 8:53 David Marchand
2022-11-18 8:53 ` [PATCH 01/11] service: fix build with " David Marchand
2022-11-18 14:47 ` Van Haaren, Harry
2022-11-18 8:53 ` [PATCH 02/11] vhost: " David Marchand
2022-11-18 10:23 ` Maxime Coquelin
2022-11-18 8:53 ` [PATCH 03/11] bus/dpaa: " David Marchand
2022-11-18 8:53 ` [PATCH 04/11] net/atlantic: " David Marchand
2022-11-18 8:53 ` [PATCH 05/11] net/dpaa2: " David Marchand
2022-11-18 8:53 ` [PATCH 06/11] net/ice: " David Marchand
2022-11-18 8:53 ` [PATCH 07/11] app/testpmd: " David Marchand
2022-11-18 8:53 ` [PATCH 08/11] app/testpmd: fix build with clang 15 in flow code David Marchand
2022-11-18 8:53 ` [PATCH 09/11] test/efd: fix build with clang 15 David Marchand
2022-11-18 8:53 ` [PATCH 10/11] test/member: " David Marchand
2022-11-18 8:53 ` [PATCH 11/11] test/event: " David Marchand
2022-11-21 1:51 ` Gao, DaxueX
[not found] ` <20221119001318.GA16784@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
2022-11-21 8:12 ` [PATCH 00/11] Fixes for " David Marchand
2022-11-21 10:23 ` 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='CAJFAV8y8QSAB7BFPQ4B0Cr2P8nEM8s=vZqDtP3wHC=ELtRY7hQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=daxuex.gao@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).