From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei Wang <wff_light@vip.163.com>
Subject: |WARNING| pw153025 [RFC 09/18] net/hinic3: add a NIC business configuration module
Date: Fri, 18 Apr 2025 11:12:07 +0200 (CEST) [thread overview]
Message-ID: <20250418091207.26715123FA7@dpdk.org> (raw)
In-Reply-To: <20250418090621.9638-10-wff_light@vip.163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153025
_coding style issues_
WARNING:TYPO_SPELLING: 'fliter' may be misspelled - perhaps 'filter'?
#1038: FILE: drivers/net/hinic3/base/hinic3_nic_cfg.c:956:
+hinic3_set_vlan_fliter(void *hwdev, u32 vlan_filter_ctrl)
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#1840: FILE: drivers/net/hinic3/base/hinic3_nic_cfg.c:1758:
+ "Failed to set rq flush, err:%d, out_param:0x%" PRIx64,
WARNING:TYPO_SPELLING: 'alos' may be misspelled - perhaps 'also'?
#2543: FILE: drivers/net/hinic3/base/hinic3_nic_cfg.h:627:
+ u8 alos;
WARNING:TYPO_SPELLING: 'fliter' may be misspelled - perhaps 'filter'?
#3310: FILE: drivers/net/hinic3/base/hinic3_nic_cfg.h:1394:
+int hinic3_set_vlan_fliter(void *hwdev, u32 vlan_filter_ctrl);
total: 0 errors, 3 warnings, 1 checks, 3355 lines checked
parent reply other threads:[~2025-04-18 9:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250418090621.9638-10-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=20250418091207.26715123FA7@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).