From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chenxu Di <chenxux.di@intel.com>
Subject: [dpdk-test-report] |WARNING| pw83669 [PATCH 2/2] net/i40e: fix incorrect FDIR flex pit
Date: Wed, 4 Nov 2020 09:46:38 +0100 (CET) [thread overview]
Message-ID: <20201104084638.2AC1CC86C@dpdk.org> (raw)
In-Reply-To: <20201104082959.63800-3-chenxux.di@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83669
_coding style issues_
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#105: FILE: drivers/net/i40e/i40e_ethdev.h:627:
+ struct i40e_fdir_flex_pit flex_pit[I40E_MAX_FLXPLD_LAYER * I40E_MAX_FLXPLD_FIED];
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#141: FILE: drivers/net/i40e/i40e_fdir.c:1776:
+ field_idx = layer_idx * I40E_MAX_FLXPLD_FIED + raw_id;
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#180: FILE: drivers/net/i40e/i40e_fdir.c:1815:
+ (layer_idx * I40E_MAX_FLXPLD_FIED);
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#186: FILE: drivers/net/i40e/i40e_fdir.c:1821:
+ field_idx = layer_idx * I40E_MAX_FLXPLD_FIED + i;
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#196: FILE: drivers/net/i40e/i40e_fdir.c:1831:
+ for (; i < I40E_MAX_FLXPLD_FIED; i++) {
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#198: FILE: drivers/net/i40e/i40e_fdir.c:1833:
+ field_idx = layer_idx * I40E_MAX_FLXPLD_FIED + i;
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#235: FILE: drivers/net/i40e/i40e_fdir.c:2015:
+ field_idx = layer_idx * I40E_MAX_FLXPLD_FIED + i;
WARNING:TYPO_SPELLING: 'FIED' may be misspelled - perhaps 'FIELD'?
#359: FILE: drivers/net/i40e/i40e_flow.c:3017:
+ field_idx = layer_idx * I40E_MAX_FLXPLD_FIED + raw_id;
total: 0 errors, 8 warnings, 0 checks, 307 lines checked
next parent reply other threads:[~2020-11-04 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201104082959.63800-3-chenxux.di@intel.com>
2020-11-04 8:46 ` checkpatch [this message]
2020-11-04 15:27 ` [dpdk-test-report] |SUCCESS| pw83669 " 0-day Robot
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=20201104084638.2AC1CC86C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chenxux.di@intel.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).