From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw86278 [PATCH v5 1/4] common/iavf: new VLAN opcode
Date: Mon, 11 Jan 2021 14:50:46 +0100 (CET) [thread overview]
Message-ID: <20210111135046.2A4782C52@dpdk.org> (raw)
In-Reply-To: <20210111133406.484200-2-haiyue.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/86278
_coding style issues_
WARNING:TYPO_SPELLING: 'sepcified' may be misspelled - perhaps 'specified'?
#232: FILE: drivers/common/iavf/virtchnl.h:674:
+ * for stripping affect the ethertype(s) sepcified for insertion and visa versa
WARNING:TYPO_SPELLING: 'stipped' may be misspelled - perhaps 'stripped'?
#254: FILE: drivers/common/iavf/virtchnl.h:696:
+ * The VF driver needs to be aware of how the tags are stipped by hardware and
WARNING:TYPO_SPELLING: 'capabilitiy' may be misspelled - perhaps 'capability'?
#457: FILE: drivers/common/iavf/virtchnl.h:1110:
+ * DCF negotiates the VIRTCHNL_VF_OFFLOAD_VLAN_V2 capabilitiy firstly to get
total: 0 errors, 3 warnings, 464 lines checked
parent reply other threads:[~2021-01-11 13:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210111133406.484200-2-haiyue.wang@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=20210111135046.2A4782C52@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haiyue.wang@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).