From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] Revert "build: disable gcc 10 zero-length-bounds warning"
Date: Mon, 14 Oct 2024 08:58:30 +0100 [thread overview]
Message-ID: <ZwzPJvPPvGP-J-vj@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20241011175710.314016-1-stephen@networkplumber.org>
On Fri, Oct 11, 2024 at 10:57:10AM -0700, Stephen Hemminger wrote:
> The zero length array warning can be re-enabled.
> The zero length marker fields are now removed by
> commit 9e152e674c77 ("mbuf: remove marker fields")
> in DPDK 24.03.
>
> This reverts commit cfacbcb5a23bc26cb913528c372adddabbb33ca1.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2024-10-14 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 17:57 Stephen Hemminger
2024-10-11 18:57 ` Morten Brørup
2024-10-14 7:58 ` Bruce Richardson [this message]
2024-10-17 17:52 ` Thomas Monjalon
2024-10-14 9:33 ` Kevin Traynor
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=ZwzPJvPPvGP-J-vj@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).