From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shaiq Wani <shaiq.wani@intel.com>
Subject: |WARNING| pw157168 [PATCH v5 1/2] net/idpf: enable AVX2 for split queue Rx
Date: Wed, 1 Oct 2025 09:57:40 +0200 (CEST) [thread overview]
Message-ID: <20251001075740.D64DB124244@dpdk.org> (raw)
In-Reply-To: <20251001075609.2608021-2-shaiq.wani@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/157168
_coding style issues_
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#246: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:512:
+ const __m256i shuf = _mm256_set_epi8(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#256: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:522:
+ const __m256i len_mask = _mm256_set_epi32(
WARNING:LONG_LINE: line length of 112 exceeds 100 columns
#317: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:583:
+ __m256i rearm0 = _mm256_permute2f128_si256(mbuf_init, _mm256_set_m128i(mb01_hi, mb01_lo), 0x20);
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#318: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:584:
+ __m256i rearm1 = _mm256_blend_epi32(mbuf_init, _mm256_set_m128i(mb01_hi, mb01_lo), 0xF0);
WARNING:LONG_LINE: line length of 112 exceeds 100 columns
#319: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:585:
+ __m256i rearm2 = _mm256_permute2f128_si256(mbuf_init, _mm256_set_m128i(mb23_hi, mb23_lo), 0x20);
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#320: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:586:
+ __m256i rearm3 = _mm256_blend_epi32(mbuf_init, _mm256_set_m128i(mb23_hi, mb23_lo), 0xF0);
total: 0 errors, 4 warnings, 2 checks, 337 lines checked
Warning in drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:
Using __builtin helpers, prefer EAL macros
parent reply other threads:[~2025-10-01 7:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251001075609.2608021-2-shaiq.wani@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=20251001075740.D64DB124244@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shaiq.wani@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).