From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Subject: [dpdk-test-report] |WARNING| pw53740 [PATCH 06/27] sched: update subport config api
Date: Tue, 28 May 2019 14:09:39 +0200 (CEST) [thread overview]
Message-ID: <20190528120939.4573A1B9D9@dpdk.org> (raw)
In-Reply-To: <20190528120553.2992-7-lukaszx.krakowiak@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/53740
_coding style issues_
WARNING:TYPO_SPELLING: 'suport' may be misspelled - perhaps 'support'?
#20:
Update suport configuration api implementation of the scheduler to allow
WARNING:BRACES: braces {} are not necessary for single statement blocks
#68: FILE: lib/librte_sched/rte_sched.c:518:
+ for (i = 0; i < RTE_SCHED_QUEUES_PER_PIPE; i++) {
+ size_per_pipe_queue_array += params->qsize[i] * sizeof(struct rte_mbuf *);
}
total: 0 errors, 2 warnings, 384 lines checked
parent reply other threads:[~2019-05-28 12:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190528120553.2992-7-lukaszx.krakowiak@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=20190528120939.4573A1B9D9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=lukaszx.krakowiak@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).