From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw41295 [24/31] net/bnxt: update HWRM API to v1.9.2.9
Date: Tue, 19 Jun 2018 23:35:36 +0200 (CEST) [thread overview]
Message-ID: <20180619213536.0DD5D1B1F7@dpdk.org> (raw)
In-Reply-To: <20180619213058.12273-25-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/41295
_coding style issues_
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#59: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:3286:
+ /* Indicates the physical function this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#71: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4098:
+ /* Indicates the physical function this event occured on. */
WARNING:LONG_LINE: line over 90 characters
#109: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4396:
+ #define HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_ID_ALLOC_FREE_NOTIFICATION \
WARNING:LONG_LINE: line over 90 characters
#134: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4421:
+ #define HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_DATA1_DEF_VNIC_STATE_MASK \
WARNING:LONG_LINE: line over 90 characters
#142: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4429:
+ #define HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_DATA1_DEF_VNIC_STATE_DEF_VNIC_ALLOC \
WARNING:LONG_LINE: line over 90 characters
#148: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4435:
+ #define HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_DATA1_DEF_VNIC_STATE_DEF_VNIC_FREE \
WARNING:LONG_LINE: line over 90 characters
#150: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4437:
+ #define HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_DATA1_DEF_VNIC_STATE_LAST \
WARNING:LONG_LINE: line over 90 characters
#151: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4438:
+ HWRM_ASYNC_EVENT_CMPL_DEFAULT_VNIC_CHANGE_EVENT_DATA1_DEF_VNIC_STATE_DEF_VNIC_FREE
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#152: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4439:
+ /* Indicates the physical function this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#157: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4444:
+ /* Indicates the virtual function this event occured on */
total: 0 errors, 10 warnings, 0 checks, 149 lines checked
parent reply other threads:[~2018-06-19 21:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180619213058.12273-25-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=20180619213536.0DD5D1B1F7@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).