From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw48331 mbuf: implement generic format for sched field
Date: Fri, 23 Nov 2018 17:54:54 +0100 (CET) [thread overview]
Message-ID: <20181123165454.7FA851B5D8@dpdk.org> (raw)
In-Reply-To: <20181123165423.134922-1-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/48331
_coding style issues_
WARNING:TYPO_SPELLING: 'accomodate' may be misspelled - perhaps 'accommodate'?
#26:
rte_sched_port to accomodate the changes made to mbuf sched field.
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#185: FILE: lib/librte_pipeline/rte_table_action.c:405:
+static uint32_t
+tm_sched_qindex(struct tm_data *data,
+ struct dscp_table_entry_data *dscp,
+ struct rte_table_action_tm_config *cfg) {
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#473: FILE: lib/librte_sched/rte_sched.h:386:
+ * @param port
+ * Handle to port scheduler instance
WARNING:LONG_LINE: line over 90 characters
#505: FILE: test/test/test_sched.c:98:
+ rte_sched_port_pkt_write(port, mbuf, SUBPORT, PIPE, TC, QUEUE, e_RTE_METER_YELLOW);
total: 1 errors, 3 warnings, 409 lines checked
parent reply other threads:[~2018-11-23 16:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20181123165423.134922-1-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=20181123165454.7FA851B5D8@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).