patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Luca Vizzarro <luca.vizzarro@arm.com>, dev@dpdk.org
Cc: luca.boccassi@gmail.com, paul.szczepanek@arm.com,
	nick.connolly@arm.com, stable@dpdk.org
Subject: Re: [PATCH 0/1] fix GCC 13 build errors on 32-bit targets
Date: Wed, 12 Jun 2024 10:29:28 +0200	[thread overview]
Message-ID: <1203ad33-9dc6-4a0a-9625-be573597c709@redhat.com> (raw)
In-Reply-To: <20240410152101.3211244-1-luca.vizzarro@arm.com>



On 4/10/24 17:21, Luca Vizzarro wrote:
> Hi everyone,
> 
> sending in a patch to resolve some build issues encountered with
> GCC 13.2 when building against 32-bit targets. These issues were
> originally reported by Luca Boccassi in one of his stable builds[1].
> Although, I have noticed that this problem presents itself on
> more versions (e.g. 21.11) as well, and it's not specific to armv7-a as
> the build suggests.
> 
> I haven't actually noticed the problem present itself on mainline,
> but it doesn't mean that it won't appear in the future. This patch
> should correctly fix this problem.
> 
> This patch is meant to target mainline, and all the currently
> supported stable versions.
> 
> [1] https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk-22.11/Debian_Next/armv7l
> 
> Luca Vizzarro (1):
>    vhost: fix GCC 13 build error
> 
>   lib/vhost/virtio_net.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 

Applied to next-virtio/for-next-net.

Thanks,
Maxime


      parent reply	other threads:[~2024-06-12  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 15:21 Luca Vizzarro
2024-04-10 15:21 ` [PATCH 1/1] vhost: fix GCC 13 build error Luca Vizzarro
2024-04-25 13:44   ` Maxime Coquelin
2024-06-12  8:29 ` Maxime Coquelin [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=1203ad33-9dc6-4a0a-9625-be573597c709@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=luca.boccassi@gmail.com \
    --cc=luca.vizzarro@arm.com \
    --cc=nick.connolly@arm.com \
    --cc=paul.szczepanek@arm.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).