From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw55331 [PATCH v2 07/28] sched: update pipe profile add API
Date: Tue, 25 Jun 2019 17:33:16 +0200 (CEST) [thread overview]
Message-ID: <20190625153316.81DC41BC06@dpdk.org> (raw)
In-Reply-To: <20190625153217.24301-8-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/55331
_coding style issues_
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#40: FILE: lib/librte_sched/rte_sched.c:353:
+ "%s: Incorrect value for parameter params
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#50: FILE: lib/librte_sched/rte_sched.c:361:
+ "%s: Incorrect value for tb rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#59: FILE: lib/librte_sched/rte_sched.c:368:
+ "%s: Incorrect value for tb size
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#71: FILE: lib/librte_sched/rte_sched.c:378:
+ "%s: Incorrect value for qsize or tc_rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#78: FILE: lib/librte_sched/rte_sched.c:385:
+ "%s: Incorrect value for be traffic class rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#89: FILE: lib/librte_sched/rte_sched.c:392:
+ "%s: Incorrect value for tc period
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#99: FILE: lib/librte_sched/rte_sched.c:400:
+ "%s: Incorrect value for tc ov weight
", __func__);
WARNING:LONG_LINE: line over 90 characters
#112: FILE: lib/librte_sched/rte_sched.c:411:
+ "%s: Incorrect value for qsize or wrr weight
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#112: FILE: lib/librte_sched/rte_sched.c:411:
+ "%s: Incorrect value for qsize or wrr weight
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#129: FILE: lib/librte_sched/rte_sched.c:896:
+ "%s: Pipe profile check failed(%d)
", __func__, status);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#145: FILE: lib/librte_sched/rte_sched.c:1358:
+ "%s: Incorrect value for parameter port
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#154: FILE: lib/librte_sched/rte_sched.c:1365:
+ "%s: Incorrect value for subport id
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#165: FILE: lib/librte_sched/rte_sched.c:1374:
+ "%s: Number of pipe profiles exceeds the max limit
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#175: FILE: lib/librte_sched/rte_sched.c:1382:
+ "%s: Pipe profile check failed(%d)
", __func__, status);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#188: FILE: lib/librte_sched/rte_sched.c:1393:
+ "%s: Pipe profile doesn't exist
", __func__);
total: 0 errors, 15 warnings, 159 lines checked
parent reply other threads:[~2019-06-25 15:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190625153217.24301-8-jasvinder.singh@intel.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=20190625153316.81DC41BC06@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jasvinder.singh@intel.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).