automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <psatheesh@marvell.com>
Subject: |WARNING| pw146344 [PATCH 2/2] net/cnxk: support rte flow on cn20k
Date: Mon, 21 Oct 2024 06:03:49 +0200 (CEST)	[thread overview]
Message-ID: <20241021040349.1BCC2123105@dpdk.org> (raw)
In-Reply-To: <20241021040144.974453-2-psatheesh@marvell.com>

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

_coding style issues_


WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#446: FILE: drivers/net/cnxk/cnxk_flow_wrapper.c:215:
+		return NULL;
+	} else {

total: 0 errors, 1 warnings, 0 checks, 431 lines checked

  parent reply	other threads:[~2024-10-21  4:03 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241021040144.974453-2-psatheesh@marvell.com>
2024-10-21  3:35 ` |SUCCESS| pw146343-146344 " qemudev
2024-10-21  3:39 ` qemudev
2024-10-21  4:03 ` checkpatch [this message]
2024-10-21  5:03 ` |FAILURE| pw146344 [dpdk-dev] " 0-day Robot
2024-10-21 21:03 ` |SUCCESS| pw146343-146344 [PATCH] [2/2] net/cnxk: support rte flow o dpdklab
2024-10-21 21:15 ` dpdklab
2024-10-21 21:24 ` dpdklab
2024-10-21 22:13 ` dpdklab
2024-10-21 23:08 ` dpdklab
2024-10-22  1:37 ` |PENDING| " dpdklab
2024-10-22  1:56 ` |FAILURE| " dpdklab
2024-10-22  1:59 ` |PENDING| " dpdklab
2024-10-22  2:02 ` |FAILURE| " dpdklab
2024-10-22  2:03 ` dpdklab
2024-10-22  2:06 ` |SUCCESS| " dpdklab
2024-10-22  2:07 ` dpdklab
2024-10-22  2:07 ` |FAILURE| " dpdklab
2024-10-22  2:08 ` dpdklab
2024-10-22  2:10 ` |SUCCESS| " dpdklab
2024-10-22  2:13 ` |FAILURE| " dpdklab
2024-10-22  2:15 ` dpdklab
2024-10-22  2:19 ` |SUCCESS| " dpdklab
2024-10-22  2:26 ` |WARNING| " dpdklab
2024-10-22  3:10 ` |SUCCESS| pw146343-146344 [PATCH 2/2] net/cnxk: support rte flow on cn20k qemudev
2024-10-22  3:10 ` qemudev
2024-10-22  3:11 ` |SUCCESS| pw146343-146344 [PATCH] [2/2] net/cnxk: support rte flow o dpdklab
2024-10-22  3:38 ` dpdklab
2024-10-22 14:51 ` |FAILURE| " dpdklab
2024-10-22 14:54 ` dpdklab
2024-10-22 14:56 ` dpdklab
2024-10-22 15:29 ` |WARNING| " dpdklab
2024-10-22 15:31 ` dpdklab
2024-10-22 15:32 ` dpdklab
2024-10-22 15:32 ` dpdklab
2024-10-22 15:33 ` dpdklab
2024-10-22 17:37 ` |FAILURE| " dpdklab
2024-10-23  3:35 ` dpdklab
2024-10-23  8:09 ` |SUCCESS| " dpdklab
2024-10-23 10:07 ` |FAILURE| " dpdklab
2024-10-23 10:10 ` dpdklab

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=20241021040349.1BCC2123105@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=psatheesh@marvell.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).