From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-test-report] |WARNING| pw27190 [PATCH pktgen 5/6] fix 32-bit build
Date: Wed, 26 Jul 2017 00:22:45 +0200 (CEST) [thread overview]
Message-ID: <20170725222245.A643637B4@dpdk.org> (raw)
In-Reply-To: <20170725222107.23203-6-thomas@monjalon.net>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/27190
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#110: FILE: app/pktgen-cmds.c:554:
+ fprintf(fd, "pktgen.jitter('%d', %" PRIu64 ");
", i, info->jitter_threshold);
ERROR:CODE_INDENT: code indent should use tabs where possible
#133: FILE: app/pktgen-latency.c:242:
+^I^I info->max_ipackets, info->rate_stats.ipackets);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#138: FILE: app/pktgen-latency.c:246:
+^I^I info->max_opackets, info->rate_stats.opackets);$
WARNING:LONG_LINE: line over 90 characters
#205: FILE: app/pktgen-port-cfg.h:341:
+ " rx_offload_capa:%4d, tx_offload_capa :%4d, reta_size :%6d, flow_type_rss_offloads:%016" PRIx64 "
",
ERROR:CODE_INDENT: code indent should use tabs where possible
#219: FILE: app/pktgen-stats.c:343:
+^I^I info->max_ipackets, rate->ipackets);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#224: FILE: app/pktgen-stats.c:347:
+^I^I info->max_opackets, rate->opackets);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#238: FILE: app/pktgen-stats.c:366:
+^I^I info->sizes.runt, info->sizes.jumbo);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#245: FILE: app/pktgen-stats.c:372:
+^I^I prev->ierrors, prev->oerrors);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#255: FILE: app/pktgen-stats.c:384:
+^I^I info->stats.arp_pkts, info->stats.echo_pkts);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#264: FILE: app/pktgen-stats.c:391:
+^I^I^I info->tx_pps, info->tx_cycles);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#314: FILE: app/pktgen-stats.c:562:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#314: FILE: app/pktgen-stats.c:562:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#315: FILE: app/pktgen-stats.c:563:
+^I^I s->ipackets, s->opackets);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#324: FILE: app/pktgen-stats.c:578:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#324: FILE: app/pktgen-stats.c:578:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#325: FILE: app/pktgen-stats.c:579:
+^I^I s->ierrors, s->imissed);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#334: FILE: app/pktgen-stats.c:595:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#334: FILE: app/pktgen-stats.c:595:
+ snprintf(buff, sizeof(buff), "%" PRIu64 "/%" PRIu64,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#335: FILE: app/pktgen-stats.c:596:
+^I^I r->ipackets, r->opackets);$
total: 14 errors, 5 warnings, 293 lines checked
parent reply other threads:[~2017-07-25 22:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170725222107.23203-6-thomas@monjalon.net>]
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=20170725222245.A643637B4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).