From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw27517 [PATCH v3 1/4] net/softnic: add softnic PMD
Date: Fri, 11 Aug 2017 14:38:07 +0200 (CEST) [thread overview]
Message-ID: <20170811123807.32E717CB0@dpdk.org> (raw)
In-Reply-To: <20170811124929.118564-2-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/27517
_coding style issues_
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#207: FILE: drivers/net/softnic/rte_eth_softnic.c:52:
+static const char *pmd_valid_args[] = {
CHECK:SPACING: No space is necessary after a cast
#341: FILE: drivers/net/softnic/rte_eth_softnic.c:186:
+ rte_ring_free((struct rte_ring *) dev->data->tx_queues[i]);
CHECK:SPACING: No space is necessary after a cast
#381: FILE: drivers/net/softnic/rte_eth_softnic.c:226:
+ return (uint16_t) rte_ring_enqueue_burst(txq,
CHECK:SPACING: No space is necessary after a cast
#382: FILE: drivers/net/softnic/rte_eth_softnic.c:227:
+ (void **) tx_pkts,
CHECK:SPACING: No space is necessary after a cast
#411: FILE: drivers/net/softnic/rte_eth_softnic.c:256:
+ (void **) &pkts[pkts_len],
CHECK:SPACING: No space is necessary after a cast
#426: FILE: drivers/net/softnic/rte_eth_softnic.c:271:
+ (uint16_t) (pkts_len - pos));
CHECK:SPACING: No space is necessary after a cast
#439: FILE: drivers/net/softnic/rte_eth_softnic.c:284:
+ (uint16_t) (pkts_len - pos));
total: 0 errors, 1 warnings, 894 lines checked
parent reply other threads:[~2017-08-11 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170811124929.118564-2-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=20170811123807.32E717CB0@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).