DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1812] net/nfp: duplicate code in branches
Date: Sat, 25 Oct 2025 18:05:24 +0000	[thread overview]
Message-ID: <bug-1812-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1812

            Bug ID: 1812
           Summary: net/nfp: duplicate code in branches
           Product: DPDK
           Version: 25.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

If DPDK is compiled with duplicate branch warnings then nfp driver has these
warnings:

[485/3707] Compiling C object drivers/...mmon_nfp.a.p/common_nfp_nfp_common.c.o
In file included from ../drivers/common/nfp/nfp_common.c:6:
../drivers/common/nfp/nfp_common.h: In function ‘nfp_qcp_read’:
../drivers/common/nfp/nfp_common.h:212:12: warning: this condition has
identical branches [-Wduplicated-branches]
  212 |         if (ptr == NFP_QCP_READ_PTR)
      |            ^

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2025-10-25 18:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1812-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.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;
as well as URLs for NNTP newsgroup(s).