automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw152415 [PATCH v5 3/3] app/test: add tests for portable version of __builtin_add_overflow
Date: Fri, 14 Mar 2025 15:34:40 +0100 (CET)	[thread overview]
Message-ID: <20250314143440.2818A123FF5@dpdk.org> (raw)
In-Reply-To: <1741962820-27123-4-git-send-email-andremue@linux.microsoft.com>

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

_coding style issues_


WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#109: FILE: app/test/test_math.c:12:
+#define TEST_MATH_RETURN_IF_ERROR(X) \
+do { \
+	if (X) { \
+		return -1; \
+	} \
+} while (0)

total: 0 errors, 1 warnings, 184 lines checked

  parent reply	other threads:[~2025-03-14 14:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1741962820-27123-4-git-send-email-andremue@linux.microsoft.com>
2025-03-14 14:01 ` |SUCCESS| pw152414-152415 " qemudev
2025-03-14 14:05 ` qemudev
2025-03-14 14:34 ` checkpatch [this message]
2025-03-14 15:31 ` |SUCCESS| pw152414-152415 [PATCH] [v5,3/3] app/test: add tests for p dpdklab
2025-03-14 15:37 ` dpdklab
2025-03-14 15:40 ` dpdklab
2025-03-14 15:41 ` dpdklab
2025-03-14 15:47 ` dpdklab
2025-03-14 15:49 ` |PENDING| " dpdklab
2025-03-14 15:54 ` |SUCCESS| " dpdklab
2025-03-14 16:00 ` dpdklab
2025-03-14 16:04 ` dpdklab
2025-03-14 16:17 ` dpdklab
2025-03-14 16:24 ` dpdklab
2025-03-14 16:36 ` dpdklab
2025-03-14 16:47 ` |SUCCESS| pw152415 [PATCH v5 3/3] app/test: add tests for portable version of __builtin_add_overflow 0-day Robot
2025-03-14 17:08 ` |SUCCESS| pw152414-152415 [PATCH] [v5,3/3] app/test: add tests for p dpdklab
2025-03-14 17:15 ` dpdklab
2025-03-14 17:17 ` dpdklab
2025-03-14 17:39 ` dpdklab
2025-03-14 18:09 ` dpdklab
2025-03-14 18:13 ` 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=20250314143440.2818A123FF5@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=andremue@linux.microsoft.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).