automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw27518 [PATCH v3 2/4] net/softnic: add traffic management support
Date: Fri, 11 Aug 2017 14:38:10 +0200 (CEST)	[thread overview]
Message-ID: <20170811123810.61B4F7CBB@dpdk.org> (raw)
In-Reply-To: <20170811124929.118564-3-jasvinder.singh@intel.com>

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

_coding style issues_


CHECK:SPACING: No space is necessary after a cast
#140: FILE: drivers/net/softnic/rte_eth_softnic.c:357:
+			(void **) &pkts_enq[pkts_enq_len],

CHECK:SPACING: No space is necessary after a cast
#178: FILE: drivers/net/softnic/rte_eth_softnic.c:395:
+			(uint16_t) (pkts_deq_len - pos));

CHECK:SPACING: No space is necessary after a cast
#290: FILE: drivers/net/softnic/rte_eth_softnic.c:664:
+		p->soft.tm.qsize[0] = (uint16_t) qsize;

CHECK:SPACING: No space is necessary after a cast
#302: FILE: drivers/net/softnic/rte_eth_softnic.c:676:
+		p->soft.tm.qsize[1] = (uint16_t) qsize;

CHECK:SPACING: No space is necessary after a cast
#314: FILE: drivers/net/softnic/rte_eth_softnic.c:688:
+		p->soft.tm.qsize[2] = (uint16_t) qsize;

CHECK:SPACING: No space is necessary after a cast
#326: FILE: drivers/net/softnic/rte_eth_softnic.c:700:
+		p->soft.tm.qsize[3] = (uint16_t) qsize;

CHECK:BRACES: Unbalanced braces around else statement
#637: FILE: drivers/net/softnic/rte_eth_softnic_tm.c:55:
+	} else

total: 0 errors, 0 warnings, 7 checks, 692 lines checked

           reply	other threads:[~2017-08-11 12:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170811124929.118564-3-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=20170811123810.61B4F7CBB@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).