From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [PATCH 0/7] fix XXX_DEBUG warnings
Date: Mon, 14 Sep 2026 14:21:11 -0700 [thread overview]
Message-ID: <20260914142111.52408ad7@phoenix.local> (raw)
In-Reply-To: <20260904191652.2399074-1-stephen@networkplumber.org>
On Fri, 4 Sep 2026 12:12:35 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> I recently modified my build test to automatically enable all
> DEBUG flags. This is because developers often add debug code,
> forget about it, and it bit rots.
>
> This patch series fixes all the places where #ifdef XXX_DEBUG
> code was present but would not build without warnings.
Applied to next-net.
Now all of next-net builds clean with this series.
next prev parent reply other threads:[~2026-09-14 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 19:12 [PATCH 0/7] fix XXX_DEBUG warnings Stephen Hemminger
2026-09-04 19:12 ` [PATCH 1/7] bus/fslmc: fix build of qbman debug code Stephen Hemminger
2026-09-10 16:51 ` hemant.agrawal
2026-09-04 19:12 ` [PATCH 2/7] bus/fslmc: fix signed comparison in buffer acquire Stephen Hemminger
2026-09-11 5:00 ` Hemant Agrawal
2026-09-04 19:12 ` [PATCH 3/7] crypto/caam_jr: fix descriptor dump build Stephen Hemminger
2026-09-11 5:01 ` Hemant Agrawal
2026-09-04 19:12 ` [PATCH 4/7] crypto/ipsec_mb: fix missing header for debug build Stephen Hemminger
2026-09-04 19:12 ` [PATCH 5/7] power/amd_uncore: fix debug log build Stephen Hemminger
2026-09-04 19:12 ` [PATCH 6/7] net/rnp: fix register debug log format Stephen Hemminger
2026-09-04 19:12 ` [PATCH 7/7] net/vmxnet3: remove unused queue dump functions Stephen Hemminger
2026-09-14 18:43 ` [PATCH 0/7] fix XXX_DEBUG warnings Stephen Hemminger
2026-09-14 21:21 ` Stephen Hemminger [this message]
2026-09-15 0:12 ` Stephen Hemminger
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=20260914142111.52408ad7@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@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