From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei Wang <wff_light@vip.163.com>
Subject: |WARNING| pw153033 [RFC 17/18] net/hinic3: add FDIR flow control module
Date: Fri, 18 Apr 2025 11:16:06 +0200 (CEST) [thread overview]
Message-ID: <20250418091606.C678E123FA7@dpdk.org> (raw)
In-Reply-To: <20250418090621.9638-18-wff_light@vip.163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153033
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#257: FILE: drivers/net/hinic3/hinic3_fdir.c:7:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'corret' may be misspelled - perhaps 'correct'?
#1322: FILE: drivers/net/hinic3/hinic3_fdir.c:1072:
+ * from the tcam and add the corret fdir rule
WARNING:TYPO_SPELLING: 'corret' may be misspelled - perhaps 'correct'?
#1339: FILE: drivers/net/hinic3/hinic3_fdir.c:1089:
+ /* Add the corret fdir rule from the tcam. */
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2060: FILE: drivers/net/hinic3/hinic3_flow.c:6:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'filterig' may be misspelled - perhaps 'filtering'?
#3367: FILE: drivers/net/hinic3/hinic3_flow.c:1313:
+ * Filter information, its used to store and manipulate packet filterig rules.
WARNING:TYPO_SPELLING: 'filterig' may be misspelled - perhaps 'filtering'?
#3413: FILE: drivers/net/hinic3/hinic3_flow.c:1359:
+ * Filter information, its used to store and manipulate packet filterig rules.
WARNING:TYPO_SPELLING: 'Unsupport' may be misspelled - perhaps 'Unsupported'?
#3574: FILE: drivers/net/hinic3/hinic3_flow.c:1520:
+ NULL, "Unsupport filter type.");
total: 0 errors, 7 warnings, 0 checks, 3721 lines checked
parent reply other threads:[~2025-04-18 9:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250418090621.9638-18-wff_light@vip.163.com>]
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=20250418091606.C678E123FA7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wff_light@vip.163.com \
/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).