From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw152398 [PATCH v4 08/10] net/ioring: support multi-segment Rx and Tx
Date: Thu, 13 Mar 2025 22:53:46 +0100 (CET) [thread overview]
Message-ID: <20250313215346.7F4C4123FF5@dpdk.org> (raw)
In-Reply-To: <20250313215151.292944-9-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152398
_coding style issues_
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#116: FILE: drivers/net/ioring/rte_eth_ioring.c:34:
+static_assert(RTE_PKTMBUF_HEADROOM >= sizeof(struct virtio_net_hdr));
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#136: FILE: drivers/net/ioring/rte_eth_ioring.c:172:
+ int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#136: FILE: drivers/net/ioring/rte_eth_ioring.c:172:
+ int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#136: FILE: drivers/net/ioring/rte_eth_ioring.c:172:
+ int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#136: FILE: drivers/net/ioring/rte_eth_ioring.c:172:
+ int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;
CHECK:BRACES: Blank lines aren't necessary before a close brace '}'
#200: FILE: drivers/net/ioring/rte_eth_ioring.c:528:
+
+}
total: 0 errors, 5 warnings, 1 checks, 302 lines checked
parent reply other threads:[~2025-03-13 21:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250313215151.292944-9-stephen@networkplumber.org>]
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=20250313215346.7F4C4123FF5@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).