From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw20231 [PATCH RFCv3 13/19] ring: allow dequeue fns to return remaining entry count
Date: Tue, 7 Feb 2017 15:14:16 +0100 (CET) [thread overview]
Message-ID: <20170207141416.45895FA3A@dpdk.org> (raw)
In-Reply-To: <1486476777-24768-14-git-send-email-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/20231
_coding style issues_
WARNING:SPACING: space prohibited before semicolon
#262: FILE: app/test/test_ring.c:395:
+ ret = rte_ring_sc_dequeue_burst(r, cur_dst, 1, NULL) ;
ERROR:CODE_INDENT: code indent should use tabs where possible
#701: FILE: examples/quota_watermark/qw/main.c:246:
+ nb_dq_pkts = rte_ring_dequeue_burst(rx, pkts, *quota, NULL);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#701: FILE: examples/quota_watermark/qw/main.c:246:
+ nb_dq_pkts = rte_ring_dequeue_burst(rx, pkts, *quota, NULL);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#710: FILE: examples/quota_watermark/qw/main.c:300:
+ nb_dq_pkts = (uint16_t) rte_ring_dequeue_burst(tx, (void *) tx_pkts,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#710: FILE: examples/quota_watermark/qw/main.c:300:
+ nb_dq_pkts = (uint16_t) rte_ring_dequeue_burst(tx, (void *) tx_pkts,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#711: FILE: examples/quota_watermark/qw/main.c:301:
+ ^I^I *quota, NULL);$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#711: FILE: examples/quota_watermark/qw/main.c:301:
+ ^I^I *quota, NULL);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#711: FILE: examples/quota_watermark/qw/main.c:301:
+ ^I^I *quota, NULL);$
total: 3 errors, 5 warnings, 767 lines checked
parent reply other threads:[~2017-02-07 14:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1486476777-24768-14-git-send-email-bruce.richardson@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=20170207141416.45895FA3A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@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).