From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw33232 [PATCH v2 2/2] net/i40e: add AVX2 Rx function
Date: Tue, 9 Jan 2018 15:34:02 +0100 (CET) [thread overview]
Message-ID: <20180109143402.46A041B1DD@dpdk.org> (raw)
In-Reply-To: <20180109143254.234428-3-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/33232
_coding style issues_
CHECK:SPACING: spaces preferred around that '*' (ctx:WxV)
#100: FILE: drivers/net/i40e/i40e_rxtx.c:3052:
+i40e_recv_pkts_vec_avx2(void __rte_unused *rx_queue,
^
CHECK:SPACING: spaces preferred around that '*' (ctx:WxO)
#101: FILE: drivers/net/i40e/i40e_rxtx.c:3053:
+ struct rte_mbuf __rte_unused **rx_pkts,
^
CHECK:SPACING: spaces preferred around that '*' (ctx:WxV)
#108: FILE: drivers/net/i40e/i40e_rxtx.c:3060:
+i40e_recv_scattered_pkts_vec_avx2(void __rte_unused *rx_queue,
^
CHECK:SPACING: spaces preferred around that '*' (ctx:WxO)
#109: FILE: drivers/net/i40e/i40e_rxtx.c:3061:
+ struct rte_mbuf __rte_unused **rx_pkts,
^
WARNING:LONG_LINE: line over 90 characters
#384: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:293:
+ (PKT_RX_EIP_CKSUM_BAD | PKT_RX_L4_CKSUM_BAD | PKT_RX_IP_CKSUM_BAD) >> 1,
WARNING:LONG_LINE: line over 90 characters
#385: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:294:
+ (PKT_RX_IP_CKSUM_GOOD | PKT_RX_EIP_CKSUM_BAD | PKT_RX_L4_CKSUM_BAD) >> 1,
WARNING:LONG_LINE: line over 90 characters
#394: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:303:
+ (PKT_RX_EIP_CKSUM_BAD | PKT_RX_L4_CKSUM_BAD | PKT_RX_IP_CKSUM_BAD) >> 1,
WARNING:LONG_LINE: line over 90 characters
#395: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:304:
+ (PKT_RX_IP_CKSUM_GOOD | PKT_RX_EIP_CKSUM_BAD | PKT_RX_L4_CKSUM_BAD) >> 1,
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 16)
#434: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:343:
+ } else
[...]
+ do {
CHECK:BRACES: Unbalanced braces around else statement
#434: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:343:
+ } else
WARNING:LONG_LINE: line over 90 characters
#575: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:484:
+ rearm6 = _mm256_blend_epi32(mbuf_init, _mm256_slli_si256(mbuf_flags, 8), 0x04);
WARNING:LONG_LINE: line over 90 characters
#576: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:485:
+ rearm4 = _mm256_blend_epi32(mbuf_init, _mm256_slli_si256(mbuf_flags, 4), 0x04);
WARNING:LONG_LINE: line over 90 characters
#578: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:487:
+ rearm0 = _mm256_blend_epi32(mbuf_init, _mm256_srli_si256(mbuf_flags, 4), 0x04);
WARNING:LONG_LINE: line over 90 characters
#593: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:502:
+ rearm7 = _mm256_blend_epi32(mbuf_init, _mm256_slli_si256(odd_flags, 8), 0x04);
WARNING:LONG_LINE: line over 90 characters
#594: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:503:
+ rearm5 = _mm256_blend_epi32(mbuf_init, _mm256_slli_si256(odd_flags, 4), 0x04);
WARNING:LONG_LINE: line over 90 characters
#596: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:505:
+ rearm1 = _mm256_blend_epi32(mbuf_init, _mm256_srli_si256(odd_flags, 4), 0x04);
total: 0 errors, 11 warnings, 5 checks, 692 lines checked
parent reply other threads:[~2018-01-09 14:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180109143254.234428-3-bruce.richardson@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=20180109143402.46A041B1DD@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@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).