From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw75432 [PATCH v4 7/8] net/dpaa: add fmc parser support for VSP
Date: Tue, 11 Aug 2020 14:38:07 +0200 (CEST) [thread overview]
Message-ID: <20200811123807.CA8811C00D@dpdk.org> (raw)
In-Reply-To: <20200811123001.30045-7-hemant.agrawal@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/75432
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <distinctionUnits>
#207: FILE: drivers/net/dpaa/dpaa_fmc.c:36:
+ struct fm_pcd_net_env_params_t distinctionUnits;
CHECK:CAMELCASE: Avoid CamelCase: <pcdParam>
#208: FILE: drivers/net/dpaa/dpaa_fmc.c:37:
+ struct ioc_fm_port_pcd_params_t pcdParam;
CHECK:CAMELCASE: Avoid CamelCase: <prsParam>
#209: FILE: drivers/net/dpaa/dpaa_fmc.c:38:
+ struct ioc_fm_port_pcd_prs_params_t prsParam;
CHECK:CAMELCASE: Avoid CamelCase: <kgParam>
#210: FILE: drivers/net/dpaa/dpaa_fmc.c:39:
+ struct ioc_fm_port_pcd_kg_params_t kgParam;
CHECK:CAMELCASE: Avoid CamelCase: <ccParam>
#211: FILE: drivers/net/dpaa/dpaa_fmc.c:40:
+ struct ioc_fm_port_pcd_cc_params_t ccParam;
CHECK:CAMELCASE: Avoid CamelCase: <vspParam>
#229: FILE: drivers/net/dpaa/dpaa_fmc.c:58:
+ ioc_fm_port_vsp_alloc_params_t vspParam;
CHECK:CAMELCASE: Avoid CamelCase: <insertData>
#265: FILE: drivers/net/dpaa/dpaa_fmc.c:94:
+ uint8_t insertData[FMC_HMANIP_MAX][FMC_INSERT_MAX];
CHECK:CAMELCASE: Avoid CamelCase: <hdr_hasNext>
#269: FILE: drivers/net/dpaa/dpaa_fmc.c:98:
+ unsigned int hdr_hasNext[FMC_HMANIP_MAX];
WARNING:TYPO_SPELLING: 'sheme' may be misspelled - perhaps 'scheme'?
#405: FILE: drivers/net/dpaa/dpaa_fmc.c:234:
+ DPAA_PMD_WARN("No VSP is assigned to sheme %d for sharemac %d!",
total: 0 errors, 1 warnings, 8 checks, 556 lines checked
parent reply other threads:[~2020-08-11 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200811123001.30045-7-hemant.agrawal@nxp.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=20200811123807.CA8811C00D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hemant.agrawal@nxp.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).