automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw157230 [PATCH v2] test/debug: fix crash with mlx5 devices
Date: Fri,  3 Oct 2025 08:52:18 +0200 (CEST)	[thread overview]
Message-ID: <20251003065218.13FA4124256@dpdk.org> (raw)
In-Reply-To: <20251003065101.617467-1-david.marchand@redhat.com>

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

_coding style issues_


ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#272: FILE: app/test/test_debug.c:144:
+	const char * prefix = "--no-shconf";

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#274: FILE: app/test/test_debug.c:146:
+	const char * prefix = "--file-prefix=debug";

total: 2 errors, 0 warnings, 173 lines checked

  parent reply	other threads:[~2025-10-03  6:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251003065101.617467-1-david.marchand@redhat.com>
2025-10-03  6:17 ` |SUCCESS| " qemudev
2025-10-03  6:22 ` qemudev
2025-10-03  6:52 ` checkpatch [this message]
2025-10-03  7:19 ` |PENDING| pw157230 [PATCH] [v2] test/debug: fix crash with mlx5 devi dpdklab
2025-10-03  7:24 ` |SUCCESS| " dpdklab
2025-10-03  7:27 ` |PENDING| " dpdklab
2025-10-03  7:27 ` |SUCCESS| " dpdklab
2025-10-03  7:31 ` |PENDING| " dpdklab
2025-10-03  7:41 ` |SUCCESS| " dpdklab
2025-10-03  7:45 ` dpdklab
2025-10-03  7:45 ` dpdklab
2025-10-03  7:46 ` dpdklab
2025-10-03  7:50 ` dpdklab
2025-10-03  7:53 ` |SUCCESS| pw157230 [PATCH v2] test/debug: fix crash with mlx5 devices 0-day Robot
2025-10-03  7:54 ` 0-day Robot
2025-10-03  7:58 ` |SUCCESS| pw157230 [PATCH] [v2] test/debug: fix crash with mlx5 devi dpdklab
2025-10-03  7:59 ` dpdklab
2025-10-03  8:01 ` dpdklab
2025-10-03  8:04 ` dpdklab
2025-10-03  8:07 ` 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=20251003065218.13FA4124256@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=david.marchand@redhat.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).