automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: |WARNING| pw110601 [PATCH] avoid AltiVec keyword vector
Date: Tue,  3 May 2022 14:05:20 +0200 (CEST)	[thread overview]
Message-ID: <20220503120520.A1816124164@dpdk.org> (raw)
In-Reply-To: <20220503120321.2438479-1-thomas@monjalon.net>

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

_coding style issues_


CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#373: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:318:
+		const __vector unsigned int len3 = vec_sl(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#380: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:322:
+		const __vector unsigned int len2 = vec_sl(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#415: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:343:
+		pkt_mb4 = (__vector unsigned char)vec_sub(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#417: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:345:
+		pkt_mb3 = (__vector unsigned char)vec_sub(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#427: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:349:
+		const __vector unsigned int len1 = vec_sl(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#430: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:352:
+		const __vector unsigned int len0 = vec_sl(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#452: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:367:
+		staterr = (__vector unsigned short)vec_mergeh(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#472: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:381:
+		pkt_mb2 = (__vector unsigned char)vec_sub(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#474: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:383:
+		pkt_mb1 = (__vector unsigned char)vec_sub(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#493: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:397:
+			__vector unsigned char eop_bits = vec_and(

total: 0 errors, 0 warnings, 2139 lines checked

       reply	other threads:[~2022-05-03 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220503120321.2438479-1-thomas@monjalon.net>
2022-05-03 12:05 ` checkpatch [this message]
2022-05-03 12:59 ` |SUCCESS| " 0-day Robot

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=20220503120520.A1816124164@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).