From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wei Huang <wei.huang@intel.com>
Subject: |WARNING| pw111773 [PATCH v1 1/2] raw/ifpga/base: add pmci driver
Date: Wed, 25 May 2022 03:45:37 +0200 (CEST) [thread overview]
Message-ID: <20220525014537.80954120945@dpdk.org> (raw)
In-Reply-To: <1653443483-30971-2-git-send-email-wei.huang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/111773
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#469: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1033:
+ max10->spi_master = spi_master;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#469: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1033:
+ max10->spi_master = spi_master;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#472: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1036:
+ max10->spi_tran_dev = spi_transaction_init(spi_master, 0);
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#524: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1228:
+ max10->spi_master = spi_master;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#524: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1228:
+ max10->spi_master = spi_master;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#527: FILE: drivers/raw/ifpga/base/ifpga_fme.c:1231:
+ max10->spi_tran_dev = spi_transaction_init(spi_master, 0);
WARNING:TYPO_SPELLING: 'CONFIGED' may be misspelled - perhaps 'CONFIGURED'?
#1359: FILE: drivers/raw/ifpga/base/opae_intel_max10.c:1051:
+ if (!GET_FIELD(PMCI_FPGA_CONFIGED, value))
WARNING:TYPO_SPELLING: 'CONFIGED' may be misspelled - perhaps 'CONFIGURED'?
#2198: FILE: drivers/raw/ifpga/base/opae_intel_max10.h:511:
+#define PMCI_FPGA_CONFIGED BIT(3)
total: 0 errors, 8 warnings, 2124 lines checked
parent reply other threads:[~2022-05-25 1:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1653443483-30971-2-git-send-email-wei.huang@intel.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=20220525014537.80954120945@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wei.huang@intel.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).