From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tomasz Duszynski <tduszynski@marvell.com>
Subject: |WARNING| pw152404 [PATCH] raw/cnxk_gpio: switch to character based GPIO interface
Date: Fri, 14 Mar 2025 13:58:34 +0100 (CET) [thread overview]
Message-ID: <20250314125834.1F2F9123FF5@dpdk.org> (raw)
In-Reply-To: <20250314125710.4118027-1-tduszynski@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152404
_coding style issues_
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#1324: FILE: drivers/raw/cnxk_gpio/cnxk_gpio_selftest.c:18:
+#define CNXK_GPIO_ERR_STR(err, str, ...) do { \
+ if (err) { \
+ CNXK_GPIO_LOG(ERR, "%s:%d: " str " (%d)", __func__, __LINE__, ##__VA_ARGS__, err); \
+ goto out; \
+ } \
} while (0)
total: 0 errors, 1 warnings, 1392 lines checked
next prev parent reply other threads:[~2025-03-14 12:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250314125710.4118027-1-tduszynski@marvell.com>
2025-03-14 12:23 ` |FAILURE| " qemudev
2025-03-14 12:58 ` checkpatch [this message]
2025-03-14 14:04 ` |SUCCESS| pw152404 [PATCH] raw/cnxk_gpio: switch to character based dpdklab
2025-03-14 14:05 ` dpdklab
2025-03-14 14:10 ` dpdklab
2025-03-14 14:20 ` dpdklab
2025-03-14 14:21 ` dpdklab
2025-03-14 14:24 ` dpdklab
2025-03-14 14:34 ` |PENDING| " dpdklab
2025-03-14 14:36 ` |SUCCESS| " dpdklab
2025-03-14 14:40 ` |FAILURE| " dpdklab
2025-03-14 14:53 ` |SUCCESS| " dpdklab
2025-03-14 14:54 ` |WARNING| " dpdklab
2025-03-14 14:56 ` dpdklab
2025-03-14 14:56 ` |FAILURE| " dpdklab
2025-03-14 15:09 ` |WARNING| " dpdklab
2025-03-14 15:09 ` |FAILURE| " dpdklab
2025-03-14 15:15 ` dpdklab
2025-03-14 15:16 ` dpdklab
2025-03-14 15:41 ` |WARNING| " dpdklab
2025-03-14 15:43 ` dpdklab
2025-03-14 15:49 ` |FAILURE| " dpdklab
2025-03-14 16:07 ` |WARNING| " dpdklab
2025-03-14 16:15 ` |FAILURE| " dpdklab
2025-03-14 16:47 ` |SUCCESS| pw152404 [PATCH] raw/cnxk_gpio: switch to character based GPIO interface 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=20250314125834.1F2F9123FF5@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=tduszynski@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).