automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yoav Winstein <yoav.w@claroty.com>
Subject: |WARNING| pw140024 [PATCH] bpf: don't verify classic bpfs
Date: Sun, 12 May 2024 07:36:17 +0200 (CEST)	[thread overview]
Message-ID: <20240512053617.4051F121E57@dpdk.org> (raw)
In-Reply-To: <20240512053542.88416-1-yoav.w@claroty.com>

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

_coding style issues_


WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

WARNING:BRACES: braces {} are not necessary for single statement blocks
#141: FILE: lib/bpf/bpf_load.c:111:
+	if (!prm->skip_verification) {
+		rc = __rte_bpf_validate(bpf);
+	}

ERROR:TRAILING_WHITESPACE: trailing whitespace
#151: FILE: lib/bpf/bpf_load.c:120:
+^I$

total: 1 errors, 2 warnings, 40 lines checked

  parent reply	other threads:[~2024-05-12  5:36 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240512053542.88416-1-yoav.w@claroty.com>
2024-05-12  5:09 ` |SUCCESS| " qemudev
2024-05-12  5:14 ` qemudev
2024-05-12  5:36 ` checkpatch [this message]
2024-05-12  6:24 ` |FAILURE| " 0-day Robot
2024-05-12  6:32 ` |SUCCESS| " dpdklab
2024-05-12  6:33 ` dpdklab
2024-05-12  6:34 ` dpdklab
2024-05-12  6:34 ` dpdklab
2024-05-12  6:35 ` dpdklab
2024-05-12  6:35 ` dpdklab
2024-05-12  6:35 ` dpdklab
2024-05-12  6:37 ` dpdklab
2024-05-12  6:37 ` dpdklab
2024-05-12  6:37 ` dpdklab
2024-05-12  6:37 ` dpdklab
2024-05-12  6:37 ` dpdklab
2024-05-12  6:38 ` dpdklab
2024-05-12  6:39 ` dpdklab
2024-05-12  6:39 ` |WARNING| " dpdklab
2024-05-12  6:40 ` |SUCCESS| " dpdklab
2024-05-12  6:40 ` dpdklab
2024-05-12  6:41 ` dpdklab
2024-05-12  6:42 ` dpdklab
2024-05-12  6:42 ` dpdklab
2024-05-12  6:42 ` dpdklab
2024-05-12  6:42 ` dpdklab
2024-05-12  6:43 ` |WARNING| " dpdklab
2024-05-12  6:43 ` |SUCCESS| " dpdklab
2024-05-12  6:44 ` dpdklab
2024-05-12  6:44 ` dpdklab
2024-05-12  6:45 ` |WARNING| " dpdklab
2024-05-12  6:45 ` |SUCCESS| " dpdklab
2024-05-12  6:45 ` dpdklab
2024-05-12  6:46 ` |WARNING| " dpdklab
2024-05-12  6:47 ` dpdklab
2024-05-12  6:48 ` |SUCCESS| " dpdklab
2024-05-12  6:50 ` dpdklab
2024-05-12  6:51 ` dpdklab
2024-05-12  6:51 ` dpdklab
2024-05-12  6:51 ` dpdklab
2024-05-12  6:52 ` |WARNING| " dpdklab
2024-05-12  6:52 ` |SUCCESS| " dpdklab
2024-05-12  6:52 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:53 ` dpdklab
2024-05-12  6:54 ` |WARNING| " dpdklab
2024-05-12  6:54 ` |SUCCESS| " dpdklab
2024-05-12  6:54 ` dpdklab
2024-05-12  6:54 ` dpdklab
2024-05-12  6:55 ` |WARNING| " dpdklab
2024-05-12  6:55 ` |SUCCESS| " dpdklab
2024-05-12  6:55 ` dpdklab
2024-05-12  6:56 ` dpdklab
2024-05-12  6:56 ` dpdklab
2024-05-12  6:56 ` dpdklab
2024-05-12  6:57 ` dpdklab
2024-05-12  6:57 ` dpdklab
2024-05-12  6:57 ` |WARNING| " dpdklab
2024-05-12  6:58 ` |SUCCESS| " dpdklab
2024-05-12  6:58 ` dpdklab
2024-05-12  7:00 ` dpdklab
2024-05-12  7:01 ` dpdklab
2024-05-12  7:03 ` dpdklab
2024-05-12  7:05 ` |WARNING| " dpdklab
2024-05-12  7:05 ` dpdklab
2024-05-12  7:05 ` |SUCCESS| " dpdklab
2024-05-12  7:07 ` dpdklab
2024-05-12  7:07 ` dpdklab
2024-05-12  7:11 ` dpdklab
2024-05-12  7:11 ` dpdklab
2024-05-12  7:13 ` dpdklab
2024-05-12  7:15 ` dpdklab
2024-05-12  7:15 ` dpdklab
2024-05-12  7:18 ` dpdklab
2024-05-12  7:19 ` dpdklab
2024-05-12  7:19 ` dpdklab
2024-05-12  7:22 ` dpdklab
2024-05-12  7:26 ` dpdklab
2024-05-12  7:29 ` dpdklab
2024-05-12  7:33 ` dpdklab
2024-05-12  7:37 ` dpdklab
2024-05-12  7:47 ` dpdklab
2024-05-12  7:56 ` dpdklab
2024-05-12  8:58 ` dpdklab
2024-05-12  9:13 ` dpdklab
2024-05-12  9:34 ` 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=20240512053617.4051F121E57@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=yoav.w@claroty.com \
    /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).