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| pw60823 [PATCH v2 3/3] net/i40e: add flow director support to avx rx path
Date: Wed,  9 Oct 2019 17:21:38 +0200 (CEST)	[thread overview]
Message-ID: <20191009152138.8F94F1E958@dpdk.org> (raw)
In-Reply-To: <20191009152006.5768-4-harry.van.haaren@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'recieve' may be misspelled - perhaps 'receive'?
#18: 
This commit adds FDIR ID support to the AVX2 based recieve

WARNING:TYPO_SPELLING: 'recieve' may be misspelled - perhaps 'receive'?
#41: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:142:
+ * rxdp: recieve descriptor ring, required to load 2nd 16B half of each desc

WARNING:LONG_LINE: line over 90 characters
#197: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:569:
+			rx_pkts[i + 0]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb0_1, 3);

WARNING:LONG_LINE: line over 90 characters
#198: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:570:
+			rx_pkts[i + 1]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb0_1, 7);

WARNING:LONG_LINE: line over 90 characters
#208: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:580:
+			rx_pkts[i + 2]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb2_3, 3);

WARNING:LONG_LINE: line over 90 characters
#209: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:581:
+			rx_pkts[i + 3]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb2_3, 7);

WARNING:LONG_LINE: line over 90 characters
#216: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:588:
+			rx_pkts[i + 4]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb4_5, 3);

WARNING:LONG_LINE: line over 90 characters
#217: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:589:
+			rx_pkts[i + 5]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb4_5, 7);

WARNING:LONG_LINE: line over 90 characters
#224: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:596:
+			rx_pkts[i + 6]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb6_7, 3);

WARNING:LONG_LINE: line over 90 characters
#225: FILE: drivers/net/i40e/i40e_rxtx_vec_avx2.c:597:
+			rx_pkts[i + 7]->hash.fdir.hi = _mm256_extract_epi32(fdir_mb6_7, 7);

total: 0 errors, 10 warnings, 0 checks, 214 lines checked

           reply	other threads:[~2019-10-09 15:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20191009152006.5768-4-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=20191009152138.8F94F1E958@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).