From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw93692 [PATCH 34/58] net/bnxt: add support for conflict resolution
Date: Tue, 1 Jun 2021 09:45:12 +0200 (CEST) [thread overview]
Message-ID: <20210601074512.1EC19120C04@dpdk.org> (raw)
In-Reply-To: <20210530085929.29695-35-venkatkumar.duvvuru@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93692
_coding style issues_
WARNING:TYPO_SPELLING: 'indentify' may be misspelled - perhaps 'identify'?
#2472: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:626:
+/* Internal Function to indentify broadcast or multicast packets */
WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'?
#2502: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:767:
+ * The priortiy field is ignored since OVS is seting it as
WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'?
#2522: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:963:
+ * The tos field is ignored since OVS is seting it as wild card
WARNING:TYPO_SPELLING: 'lable' may be misspelled - perhaps 'label'?
#2546: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:1108:
+ * The TC and flow lable field are ignored since OVS is seting
WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'?
#2546: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:1108:
+ * The TC and flow lable field are ignored since OVS is seting
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8681: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:666:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL2 = 3,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8682: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:667:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL3 = 8,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8683: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:668:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL4 = 9,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8684: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:669:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TUN = 10,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8685: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:670:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L2 = 11,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8686: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:671:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L3 = 12,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8687: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:672:
+ BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L4 = 13,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8899: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:884:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL2 = 3,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8900: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:885:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL3 = 8,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8901: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:886:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL4 = 9,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8902: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:887:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TUN = 10,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8903: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:888:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L2 = 11,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8904: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:889:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L3 = 12,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8905: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:890:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L4 = 13,
WARNING:TYPO_SPELLING: 'resoution' may be misspelled - perhaps 'resolution'?
#80039: FILE: drivers/net/bnxt/tf_ulp/ulp_template_struct.h:221:
+ /* conflict resoution opcode */
total: 0 errors, 20 warnings, 0 checks, 80177 lines checked
parent reply other threads:[~2021-06-01 7:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210530085929.29695-35-venkatkumar.duvvuru@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=20210601074512.1EC19120C04@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=venkatkumar.duvvuru@broadcom.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).