From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw94170 [PATCH v2 34/58] net/bnxt: add support to identify duplicate flows
Date: Mon, 14 Jun 2021 16:42:38 +0200 (CEST) [thread overview]
Message-ID: <20210614144238.71004121198@dpdk.org> (raw)
In-Reply-To: <20210613000652.28191-35-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94170
_coding style issues_
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#8517: 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'?
#8518: 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'?
#8519: 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'?
#8520: 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'?
#8521: 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'?
#8522: 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'?
#8523: 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'?
#8735: 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'?
#8736: 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'?
#8737: 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'?
#8738: 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'?
#8739: 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'?
#8740: 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'?
#8741: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:890:
+ BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L4 = 13,
total: 0 errors, 14 warnings, 0 checks, 80027 lines checked
parent reply other threads:[~2021-06-14 14:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210613000652.28191-35-ajit.khaparde@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=20210614144238.71004121198@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).