From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stephen@networkplumber.org>
Subject: RE: [PATCH] net/ice/base: allow array bounds warnings
Date: Thu, 13 Aug 2026 13:48:12 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F659DF@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260813111509.1446335-1-bruce.richardson@intel.com>
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Thursday, 13 August 2026 13.15
>
> Since there are no zero-length arrays in the base code any more, remove
> the -Wno-array-bounds build flag.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> drivers/net/intel/ice/base/meson.build | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/net/intel/ice/base/meson.build
> b/drivers/net/intel/ice/base/meson.build
> index fd079c41cf..da961f0752 100644
> --- a/drivers/net/intel/ice/base/meson.build
> +++ b/drivers/net/intel/ice/base/meson.build
> @@ -44,11 +44,6 @@ else
> ]
> endif
>
> -# Bugzilla ID: 678
> -if (toolchain == 'gcc' and cc.version().version_compare('>=11.0.0'))
> - error_cflags += ['-Wno-array-bounds']
> -endif
> -
Good catch!
Consequential workarounds like this are often overlooked when the workaround is not necessary anymore.
Patchwork should have a "fixed/workaround" state for tracking workarounds, so they can be properly cleaned up like this.
The root cause has been fixed, so by removing this last detail of the workaround the bug is truly "fixed/resolved".
Acked-by: Morten Brørup <mb@smartsharesystems.com>
prev parent reply other threads:[~2026-08-13 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 9:00 ice driver compiler warning Morten Brørup
2026-08-01 15:22 ` Stephen Hemminger
2026-08-13 11:15 ` [PATCH] net/ice/base: allow array bounds warnings Bruce Richardson
2026-08-13 11:48 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35F659DF@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=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