From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw79407 [PATCH 2/2] net/bnxt: update HWRM structures
Date: Thu, 1 Oct 2020 06:00:41 +0200 (CEST) [thread overview]
Message-ID: <20201001040041.E28F81D66E@dpdk.org> (raw)
In-Reply-To: <20201001035619.67824-3-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/79407
_coding style issues_
WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#365: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1575:
+ uint8_t write_thru_table_type;
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#379: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1589:
+ #define CFA_BDS_WRITE_CMD_DATA_MSG_WRITE_THRU UINT32_C(0x10)
WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#471: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1681:
+ uint8_t write_thru;
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#478: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1688:
+ #define CFA_BDS_EM_INSERT_CMD_DATA_MSG_WRITE_THRU UINT32_C(0x10)
WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#519: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1729:
+ uint8_t write_thru;
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#526: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1736:
+ #define CFA_BDS_EM_DELETE_CMD_DATA_MSG_WRITE_THRU UINT32_C(0x10)
total: 0 errors, 6 warnings, 0 checks, 11693 lines checked
parent reply other threads:[~2020-10-01 4:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201001035619.67824-3-ajit.khaparde@broadcom.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=20201001040041.E28F81D66E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.com \
--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).