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| pw149154 [PATCH v2 1/8] net/ioring: introduce new driver
Date: Wed, 11 Dec 2024 17:30:49 +0100 (CET)	[thread overview]
Message-ID: <20241211163049.A3B4C121F12@dpdk.org> (raw)
In-Reply-To: <20241211162904.121695-2-stephen@networkplumber.org>

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

_coding style issues_


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

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

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

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#309: FILE: drivers/net/ioring/rte_eth_ioring.c:76:
+#ifdef IFF_NAPI

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#311: FILE: drivers/net/ioring/rte_eth_ioring.c:78:
+	if (features & IFF_NAPI)

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#312: FILE: drivers/net/ioring/rte_eth_ioring.c:79:
+		flags |= IFF_NAPI;

WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#393: FILE: drivers/net/ioring/rte_eth_ioring.c:160:
+	ifr.ifr_flags = IFF_DETACH_QUEUE;

total: 0 errors, 7 warnings, 0 checks, 366 lines checked

           reply	other threads:[~2024-12-11 16:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20241211162904.121695-2-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=20241211163049.A3B4C121F12@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).