automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw152340 [PATCH v3 9/9] net/ioring: support multi-segment Rx and Tx
Date: Wed, 12 Mar 2025 00:56:56 +0100 (CET)	[thread overview]
Message-ID: <20250311235656.52F541206A9@dpdk.org> (raw)
In-Reply-To: <20250311235424.172440-10-stephen@networkplumber.org>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152340

_coding style issues_


WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#130: FILE: drivers/net/ioring/rte_eth_ioring.c:173:
+	int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#130: FILE: drivers/net/ioring/rte_eth_ioring.c:173:
+	int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#130: FILE: drivers/net/ioring/rte_eth_ioring.c:173:
+	int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#130: FILE: drivers/net/ioring/rte_eth_ioring.c:173:
+	int flags = IFF_TAP | IFF_MULTI_QUEUE | IFF_NO_PI | IFF_VNET_HDR;

total: 0 errors, 4 warnings, 0 checks, 225 lines checked

  parent reply	other threads:[~2025-03-11 23:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250311235424.172440-10-stephen@networkplumber.org>
2025-03-11 23:21 ` |SUCCESS| pw152332-152340 " qemudev
2025-03-11 23:26 ` qemudev
2025-03-11 23:56 ` checkpatch [this message]
2025-03-12  0:41 ` |SUCCESS| pw152332-152340 [PATCH] [v3,9/9] net/ioring: support multi dpdklab
2025-03-12  0:47 ` |SUCCESS| pw152340 [PATCH v3 9/9] net/ioring: support multi-segment Rx and Tx 0-day Robot
2025-03-12  0:47 ` |SUCCESS| pw152332-152340 [PATCH] [v3,9/9] net/ioring: support multi dpdklab
2025-03-12  0:56 ` dpdklab
2025-03-12  1:09 ` dpdklab
2025-03-12  1:12 ` dpdklab
2025-03-12  1:21 ` dpdklab
2025-03-12  1:29 ` dpdklab
2025-03-12  1:36 ` dpdklab
2025-03-12  1:56 ` dpdklab
2025-03-12  1:59 ` dpdklab
2025-03-12  1:59 ` dpdklab
2025-03-12  2:03 ` dpdklab
2025-03-12  2:26 ` dpdklab
2025-03-12  2:29 ` dpdklab
2025-03-12  2:29 ` dpdklab
2025-03-12  2:45 ` dpdklab
2025-03-12  2:57 ` dpdklab
2025-03-12  3:38 ` dpdklab
2025-03-12  3:39 ` dpdklab

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=20250311235656.52F541206A9@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).