From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw159125 [PATCH 2/2] app/test: make parameters clearer when adding fast tests
Date: Tue, 2 Dec 2025 16:50:25 +0100 (CET) [thread overview]
Message-ID: <20251202155025.1B5A4126217@dpdk.org> (raw)
In-Reply-To: <20251202154948.1757169-3-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159125
_coding style issues_
WARNING:MACRO_ARG_UNUSED: Argument 'no_huge' is not used in function-like macro
#233: FILE: app/test/test.h:219:
+#define REGISTER_FAST_TEST(cmd, no_huge, ASan, func) REGISTER_TEST_COMMAND(cmd, func)
WARNING:MACRO_ARG_UNUSED: Argument 'ASan' is not used in function-like macro
#233: FILE: app/test/test.h:219:
+#define REGISTER_FAST_TEST(cmd, no_huge, ASan, func) REGISTER_TEST_COMMAND(cmd, func)
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#568: FILE: app/test/test_event_eth_tx_adapter.c:1013:
+REGISTER_FAST_TEST(event_eth_tx_adapter_autotest, HUGEPAGES, ASAN, test_event_eth_tx_adapter_common);
total: 0 errors, 3 warnings, 683 lines checked
next prev parent reply other threads:[~2025-12-02 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251202154948.1757169-3-bruce.richardson@intel.com>
2025-12-02 15:16 ` |SUCCESS| pw159124-159125 " qemudev
2025-12-02 15:21 ` qemudev
2025-12-02 15:50 ` checkpatch [this message]
2025-12-02 17:54 ` |PENDING| pw159124-159125 [PATCH] [2/2] app/test: make parameters cl dpdklab
2025-12-02 17:55 ` dpdklab
2025-12-02 17:57 ` dpdklab
2025-12-02 18:08 ` dpdklab
2025-12-02 18:21 ` |SUCCESS| " dpdklab
2025-12-02 18:33 ` dpdklab
2025-12-02 18:34 ` dpdklab
2025-12-02 18:55 ` dpdklab
2025-12-02 18:59 ` |FAILURE| pw159125 [PATCH 2/2] app/test: make parameters clearer when adding fast tests 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=20251202155025.1B5A4126217@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@intel.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).