From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw78710 [PATCH v3 43/60] common/sfc_efx/base: add function control window concept
Date: Thu, 24 Sep 2020 14:19:35 +0200 (CEST) [thread overview]
Message-ID: <20200924121935.B79721E4BB@dpdk.org> (raw)
In-Reply-To: <1600949555-28043-44-git-send-email-arybchenko@solarflare.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/78710
_coding style issues_
WARNING:TYPO_SPELLING: 'READD' may be misspelled - perhaps 'RE-ADD'?
#153: FILE: drivers/common/sfc_efx/base/ef10_mcdi.c:244:
+ EFX_BAR_FCW_READD(enp, ER_GZ_MC_SFT_STATUS, &dword);
WARNING:TYPO_SPELLING: 'READD' may be misspelled - perhaps 'RE-ADD'?
#157: FILE: drivers/common/sfc_efx/base/ef10_mcdi.c:248:
+ EFX_BAR_READD(enp, ER_DZ_BIU_MC_SFT_STATUS_REG,
WARNING:TYPO_SPELLING: 'READD' may be misspelled - perhaps 'RE-ADD'?
#211: FILE: drivers/common/sfc_efx/base/efx_impl.h:1234:
+#define EFX_BAR_FCW_READD(_enp, _reg, _edp) \
WARNING:TYPO_SPELLING: 'READD' may be misspelled - perhaps 'RE-ADD'?
#214: FILE: drivers/common/sfc_efx/base/efx_impl.h:1237:
+ EFSYS_BAR_READD((_enp)->en_esbp, _reg ## _OFST + \
WARNING:TYPO_SPELLING: 'readd' may be misspelled - perhaps 're-add'?
#217: FILE: drivers/common/sfc_efx/base/efx_impl.h:1240:
+ EFSYS_PROBE3(efx_bar_fcw_readd, const char *, #_reg, \
WARNING:TYPO_SPELLING: 'READD' may be misspelled - perhaps 'RE-ADD'?
#303: FILE: drivers/common/sfc_efx/base/rhead_nic.c:459:
+ EFX_BAR_FCW_READD(enp, ER_GZ_MC_SFT_STATUS, &dword);
total: 0 errors, 6 warnings, 0 checks, 168 lines checked
parent reply other threads:[~2020-09-24 12:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1600949555-28043-44-git-send-email-arybchenko@solarflare.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=20200924121935.B79721E4BB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arybchenko@solarflare.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).