From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw48693 [v3, 31/34] net/ice: support advance RX/TX
Date: Wed, 12 Dec 2018 08:03:48 +0100 (CET) [thread overview]
Message-ID: <20181212070349.002D31B490@dpdk.org> (raw)
In-Reply-To: <1544598004-27099-32-git-send-email-wenzhuo.lu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/48693
_coding style issues_
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#75: FILE: drivers/net/ice/ice_lan_rxtx.c:998:
+ qword1 = rte_le_to_cpu_64(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#92: FILE: drivers/net/ice/ice_lan_rxtx.c:1015:
+ qword1 = rte_le_to_cpu_64(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#103: FILE: drivers/net/ice/ice_lan_rxtx.c:1026:
+ rte_le_to_cpu_32(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#105: FILE: drivers/net/ice/ice_lan_rxtx.c:1028:
+ mb->packet_type = ptype_tbl[(uint8_t)(
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'ice_rx_scan_hw_ring', this function's name, in a string
#125: FILE: drivers/net/ice/ice_lan_rxtx.c:1048:
+ PMD_RX_LOG(DEBUG, "ice_rx_scan_hw_ring: "
WARNING:TYPO_SPELLING: 'regsiter' may be misspelled - perhaps 'register'?
#189: FILE: drivers/net/ice/ice_lan_rxtx.c:1112:
+ /* Update rx tail regsiter */
CHECK:SPACING: spaces preferred around that '*' (ctx:WxV)
#275: FILE: drivers/net/ice/ice_lan_rxtx.c:1198:
+ice_recv_pkts_bulk_alloc(void __rte_unused *rx_queue,
^
CHECK:SPACING: spaces preferred around that '*' (ctx:WxO)
#276: FILE: drivers/net/ice/ice_lan_rxtx.c:1199:
+ struct rte_mbuf __rte_unused **rx_pkts,
^
CHECK:BRACES: Unbalanced braces around else statement
#413: FILE: drivers/net/ice/ice_lan_rxtx.c:1336:
+ } else
total: 0 errors, 2 warnings, 7 checks, 695 lines checked
parent reply other threads:[~2018-12-12 7:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1544598004-27099-32-git-send-email-wenzhuo.lu@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=20181212070349.002D31B490@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wenzhuo.lu@intel.com \
/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).