automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-test-report] |WARNING| pw19446 [PATCH 13/15] event/sw: add dump function for easier debugging
Date: Mon, 16 Jan 2017 16:41:53 +0100 (CET)	[thread overview]
Message-ID: <20170116154153.D3465F963@dpdk.org> (raw)
In-Reply-To: <1484581255-148720-14-git-send-email-harry.van.haaren@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/19446

_coding style issues_


WARNING:LONG_LINE_STRING: line over 90 characters
#88: FILE: drivers/event/sw/sw_evdev.c:433:
+		fprintf(f, "	rx   %"PRIu64"	drop %"PRIu64"	tx   %"PRIu64"	inflight %d
",

ERROR:SPACING: spaces required around that '>' (ctx:OxW)
#99: FILE: drivers/event/sw/sw_evdev.c:444:
+		for (max = (int)RTE_DIM(p->poll_buckets); max --> 0;)
 		                                                ^

WARNING:LONG_LINE: line over 90 characters
#107: FILE: drivers/event/sw/sw_evdev.c:452:
+						p->poll_buckets[j] * 100.0 / p->total_polls);

total: 1 errors, 2 warnings, 121 lines checked

           reply	other threads:[~2017-01-16 15:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1484581255-148720-14-git-send-email-harry.van.haaren@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=20170116154153.D3465F963@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=harry.van.haaren@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).