From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw159574 [RFC] bsd_pbf: introduce new driver using FreeBSD /dev/bpf
Date: Mon, 5 Jan 2026 07:55:31 +0100 (CET) [thread overview]
Message-ID: <20260105065531.6394B124270@dpdk.org> (raw)
In-Reply-To: <20260105065344.70462-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159574
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#372: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:87:
+ unsigned nb_queues;
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#388: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:103:
+static const char *valid_arguments[] = {
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#490: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:205:
+ unsigned i;
CHECK:BRACES: Unbalanced braces around else statement
#518: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:233:
+ } else
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#689: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:404:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#770: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:485:
+ unsigned i;
CHECK:BRACES: Unbalanced braces around else statement
#810: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:525:
+ } else
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1085: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:800:
+ const unsigned nb_queues,
WARNING:BRACES: braces {} are not necessary for single statement blocks
#1206: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:921:
+ if (zerocopy) {
+ PMD_LOG(WARNING, "Zero-copy BPF not supported on this platform");
+ }
CHECK:BRACES: Unbalanced braces around else statement
#1325: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:1040:
+ } else
CHECK:BRACES: Unbalanced braces around else statement
#1382: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:1097:
+ } else
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1406: FILE: drivers/net/bsd_bpf/rte_eth_bpf.c:1121:
+ unsigned k_idx;
total: 0 errors, 8 warnings, 4 checks, 1405 lines checked
Warning in drivers/net/bsd_bpf/rte_eth_bpf.c:
Using __atomic_xxx/__ATOMIC_XXX built-ins, prefer rte_atomic_xxx/rte_memory_order_xxx
next parent reply other threads:[~2026-01-05 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260105065344.70462-1-stephen@networkplumber.org>
2026-01-05 6:55 ` checkpatch [this message]
2026-01-05 7:08 ` |SUCCESS| " qemudev
2026-01-05 7:13 ` qemudev
2026-01-05 7:44 ` 0-day Robot
2026-01-05 7:44 ` 0-day Robot
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=20260105065531.6394B124270@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=test-report@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).