From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw70640 [PATCH 34/37] net/dpaa2: flow API QoS setup follows FS setup
Date: Wed, 27 May 2020 15:34:28 +0200 (CEST) [thread overview]
Message-ID: <20200527133428.1496B1DAEE@dpdk.org> (raw)
In-Reply-To: <20200527132326.1382-35-hemant.agrawal@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/70640
_coding style issues_
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#156: FILE: drivers/net/dpaa2/dpaa2_flow.c:3354:
+ if (dpkg_prepare_key_cfg(
WARNING:LONG_LINE: line over 90 characters
#158: FILE: drivers/net/dpaa2/dpaa2_flow.c:3356:
+ (uint8_t *)(size_t)priv->extract.qos_extract_param) < 0) {
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#159: FILE: drivers/net/dpaa2/dpaa2_flow.c:3357:
+ DPAA2_PMD_ERR(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#179: FILE: drivers/net/dpaa2/dpaa2_flow.c:3373:
+ DPAA2_PMD_ERR(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#222: FILE: drivers/net/dpaa2/dpaa2_flow.c:3426:
+ DPAA2_PMD_ERR(
WARNING:LONG_LINE: line over 90 characters
#223: FILE: drivers/net/dpaa2/dpaa2_flow.c:3427:
+ "Error in addnig entry to QoS table(%d)", ret);
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#258: FILE: drivers/net/dpaa2/dpaa2_flow.c:3862:
+ DPAA2_PMD_ERR(
WARNING:LONG_LINE: line over 90 characters
#259: FILE: drivers/net/dpaa2/dpaa2_flow.c:3863:
+ "Error in removing entry from QoS table(%d)", ret);
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#285: FILE: drivers/net/dpaa2/dpaa2_flow.c:3882:
+ DPAA2_PMD_ERR(
total: 0 errors, 3 warnings, 6 checks, 214 lines checked
parent reply other threads:[~2020-05-27 13:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200527132326.1382-35-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=20200527133428.1496B1DAEE@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).