From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw55330 [PATCH v2 06/28] sched: update subport config API
Date: Tue, 25 Jun 2019 17:33:15 +0200 (CEST) [thread overview]
Message-ID: <20190625153315.38FA21BC05@dpdk.org> (raw)
In-Reply-To: <20190625153217.24301-7-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/55330
_coding style issues_
WARNING:TYPO_SPELLING: 'suport' may be misspelled - perhaps 'support'?
#17:
Update suport configuration api implementation to allow
WARNING:BRACES: braces {} are not necessary for single statement blocks
#129: FILE: lib/librte_sched/rte_sched.c:515:
+ for (i = 0; i < RTE_SCHED_QUEUES_PER_PIPE; i++) {
+ size_per_pipe_queue_array += params->qsize[i] * sizeof(struct rte_mbuf *);
}
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#395: FILE: lib/librte_sched/rte_sched.c:785:
+ "%s: Incorrect value for parameter params
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#401: FILE: lib/librte_sched/rte_sched.c:791:
+ "%s: Incorrect value for tb rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#407: FILE: lib/librte_sched/rte_sched.c:797:
+ "%s: Incorrect value for tb size
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#414: FILE: lib/librte_sched/rte_sched.c:804:
+ "%s: Incorrect value for tc rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#420: FILE: lib/librte_sched/rte_sched.c:810:
+ "%s: Incorrect value for tc period
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#428: FILE: lib/librte_sched/rte_sched.c:818:
+ "%s: Incorrect value for pipes number
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#444: FILE: lib/librte_sched/rte_sched.c:834:
+ "%s: Incorrect value for tc rate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#461: FILE: lib/librte_sched/rte_sched.c:851:
+ "%s: Incorrect value for wrr weights
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#470: FILE: lib/librte_sched/rte_sched.c:860:
+ "%s: Incorrect value for number of pipe profiles
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#486: FILE: lib/librte_sched/rte_sched.c:876:
+ "%s: Incorrect value for parameter port
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#492: FILE: lib/librte_sched/rte_sched.c:882:
+ "%s: Incorrect value for subport id
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#596: FILE: lib/librte_sched/rte_sched.c:1062:
+ "%s: Fail to determine the memory to allocate
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#609: FILE: lib/librte_sched/rte_sched.c:1071:
+ "%s: Memory allocation fails
", __func__);
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#707: FILE: lib/librte_sched/rte_sched.c:1177:
+ "%s: Subport bitmap init error
", __func__);
total: 0 errors, 16 warnings, 766 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-7-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=20190625153315.38FA21BC05@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).