From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw93694 [PATCH 39/58] net/bnxt: refactor TF ULP
Date: Tue, 1 Jun 2021 10:00:51 +0200 (CEST) [thread overview]
Message-ID: <20210601080051.E70A1120C04@dpdk.org> (raw)
In-Reply-To: <20210530085929.29695-40-venkatkumar.duvvuru@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93694
_coding style issues_
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#2432: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:901:
+ [BNXT_ULP_CLASS_HID_daa7] = 883,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#3131: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:1600:
+ [BNXT_ULP_CLASS_HID_2daa7] = 1582,
WARNING:TYPO_SPELLING: 'bae' may be misspelled - perhaps 'base'?
#3733: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:2202:
+ [BNXT_ULP_CLASS_HID_1bae] = 2184,
WARNING:TYPO_SPELLING: 'afe' may be misspelled - perhaps 'safe'?
#4126: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:2595:
+ [BNXT_ULP_CLASS_HID_afe0] = 2577,
WARNING:TYPO_SPELLING: 'ede' may be misspelled - perhaps 'edge'?
#4425: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:2894:
+ [BNXT_ULP_CLASS_HID_ede4] = 2876,
WARNING:TYPO_SPELLING: 'ded' may be misspelled - perhaps 'dead'?
#4975: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:3444:
+ [BNXT_ULP_CLASS_HID_2ded0] = 3426,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#22879: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:20809:
+ .class_hid = BNXT_ULP_CLASS_HID_daa7,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#37089: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:35019:
+ .class_hid = BNXT_ULP_CLASS_HID_2daa7,
WARNING:TYPO_SPELLING: 'bae' may be misspelled - perhaps 'base'?
#48792: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:46722:
+ .class_hid = BNXT_ULP_CLASS_HID_1bae,
WARNING:TYPO_SPELLING: 'afe' may be misspelled - perhaps 'safe'?
#56382: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:54312:
+ .class_hid = BNXT_ULP_CLASS_HID_afe0,
WARNING:TYPO_SPELLING: 'ede' may be misspelled - perhaps 'edge'?
#62509: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:60439:
+ .class_hid = BNXT_ULP_CLASS_HID_ede4,
WARNING:TYPO_SPELLING: 'ded' may be misspelled - perhaps 'dead'?
#73666: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_class.c:71596:
+ .class_hid = BNXT_ULP_CLASS_HID_2ded0,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#84093: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:1863:
+ BNXT_ULP_CLASS_HID_daa7 = 0xdaa7,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#84792: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:2562:
+ BNXT_ULP_CLASS_HID_2daa7 = 0x2daa7,
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#84792: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:2562:
+ BNXT_ULP_CLASS_HID_2daa7 = 0x2daa7,
WARNING:TYPO_SPELLING: 'bae' may be misspelled - perhaps 'base'?
#85394: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:3164:
+ BNXT_ULP_CLASS_HID_1bae = 0x1bae,
WARNING:TYPO_SPELLING: 'bae' may be misspelled - perhaps 'base'?
#85394: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:3164:
+ BNXT_ULP_CLASS_HID_1bae = 0x1bae,
WARNING:TYPO_SPELLING: 'afe' may be misspelled - perhaps 'safe'?
#85791: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:3557:
+ BNXT_ULP_CLASS_HID_afe0 = 0xafe0,
WARNING:TYPO_SPELLING: 'ede' may be misspelled - perhaps 'edge'?
#86090: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:3856:
+ BNXT_ULP_CLASS_HID_ede4 = 0xede4,
WARNING:TYPO_SPELLING: 'ded' may be misspelled - perhaps 'dead'?
#86640: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:4406:
+ BNXT_ULP_CLASS_HID_2ded0 = 0x2ded0,
WARNING:TYPO_SPELLING: 'ded' may be misspelled - perhaps 'dead'?
#86640: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:4406:
+ BNXT_ULP_CLASS_HID_2ded0 = 0x2ded0,
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#90470: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:1283:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TUN},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#90752: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:1565:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TUN},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#91818: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2631:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL2},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#91821: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2634:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L2}
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#92076: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2889:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL2},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#92079: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2892:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L2}
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#93290: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:4234:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL2},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#93294: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:4237:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L2}
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#93471: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:4492:
+ ULP_WP_SYM_DECAP_FUNC_THRU_TL2},
WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#93474: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:4495:
+ ULP_WP_SYM_DECAP_FUNC_THRU_L2}
total: 0 errors, 31 warnings, 0 checks, 109516 lines checked
parent reply other threads:[~2021-06-01 8:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210530085929.29695-40-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=20210601080051.E70A1120C04@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).