From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei <wff_light@vip.163.com>
Subject: |WARNING| pw153854 [PATCH v1 15/18] net/hinic3: add MML and EEPROM access feature
Date: Thu, 29 May 2025 10:22:46 +0200 (CEST) [thread overview]
Message-ID: <20250529082246.47506125275@dpdk.org> (raw)
In-Reply-To: <20250529081529.2839-16-wff_light@vip.163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153854
_coding style issues_
WARNING:TYPO_SPELLING: 'slq' may be misspelled - perhaps 'sql'?
#1507: FILE: drivers/net/hinic3/mml/hinic3_mml_lib.h:140:
+ void *slq_handle;
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#1912: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.c:91:
+ hinic3_pmd_mml_log(self->show_str, &self->show_len, "buf_addr:0x%" PRIx64,
CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#2076: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.c:255:
+ "cla_addr:0x%" PRIu64,
CHECK:CAMELCASE: Avoid CamelCase: <PRId64>
#2079: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.c:258:
+ "doorbell phy_addr:0x%" PRId64,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2171: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.c:350:
+ "slave_port_id:%u", task->bs2.slave_port_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2171: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.c:350:
+ "slave_port_id:%u", task->bs2.slave_port_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#2633: FILE: drivers/net/hinic3/mml/hinic3_mml_queue.h:62:
+ unsigned int slave_port_id : 2;
total: 0 errors, 4 warnings, 3 checks, 2729 lines checked
parent reply other threads:[~2025-05-29 8:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250529081529.2839-16-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=20250529082246.47506125275@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).