From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw93693 [PATCH 35/58] net/bnxt: add support for conditional goto processing
Date: Tue, 1 Jun 2021 09:46:48 +0200 (CEST) [thread overview]
Message-ID: <20210601074648.60802120C04@dpdk.org> (raw)
In-Reply-To: <20210530085929.29695-36-venkatkumar.duvvuru@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93693
_coding style issues_
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5573: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:672:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL2 = 3,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5574: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:673:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL3 = 8,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5575: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:674:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL4 = 9,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5576: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:675:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TUN = 10,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5577: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:676:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L2 = 11,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5578: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:677:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L3 = 12,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5579: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:678:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L4 = 13,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5791: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:890:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TL2 = 3,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5792: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:891:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TL3 = 8,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5793: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:892:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TL4 = 9,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5794: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:893:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TUN = 10,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5795: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:894:
+ ULP_SR_SYM_DECAP_FUNC_THRU_L2 = 11,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5796: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:895:
+ ULP_SR_SYM_DECAP_FUNC_THRU_L3 = 12,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#5797: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:896:
+ ULP_SR_SYM_DECAP_FUNC_THRU_L4 = 13,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#7031: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_stingray_act.c:399:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TUN},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#7407: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_stingray_act.c:653:
+ ULP_SR_SYM_DECAP_FUNC_THRU_TUN},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#17962: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:397:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TUN},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#18338: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:651:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TUN},
total: 0 errors, 18 warnings, 0 checks, 27930 lines checked
parent reply other threads:[~2021-06-01 7:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210530085929.29695-36-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=20210601074648.60802120C04@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).