From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: |WARNING| pw148308 [PATCH v10 7/7] test: add stress test suite
Date: Mon, 11 Nov 2024 14:29:59 +0100 (CET) [thread overview]
Message-ID: <20241111132959.B9928123151@dpdk.org> (raw)
In-Reply-To: <20241111141910.40604-8-konstantin.ananyev@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148308
_coding style issues_
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#65:
DPDK:stress-tests / soring_stress_autotest
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#144: FILE: app/test/test_soring_stress.c:48:
+REGISTER_STRESS_TEST(soring_stress_autotest, test_ring_stress);
total: 0 errors, 2 warnings, 44 lines checked
Warning in app/test/test.h:
Using REGISTER_TEST_COMMAND instead of REGISTER_<suite_name>_TEST
next prev parent reply other threads:[~2024-11-11 13:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111141910.40604-8-konstantin.ananyev@huawei.com>
2024-11-11 12:59 ` |SUCCESS| pw148304-148308 " qemudev
2024-11-11 13:04 ` qemudev
2024-11-11 13:29 ` checkpatch [this message]
2024-11-11 14:25 ` |SUCCESS| pw148308 " 0-day Robot
2024-11-11 16:25 ` |SUCCESS| pw148304-148308 [PATCH] [v10,7/7] test: add stress test su dpdklab
2024-11-11 16:26 ` dpdklab
2024-11-11 16:33 ` dpdklab
2024-11-11 16:36 ` dpdklab
2024-11-11 16:39 ` dpdklab
2024-11-11 16:40 ` dpdklab
2024-11-11 17:08 ` |PENDING| " dpdklab
2024-11-11 17:23 ` |SUCCESS| " dpdklab
2024-11-11 17:26 ` dpdklab
2024-11-11 17:27 ` dpdklab
2024-11-11 17:37 ` |PENDING| " dpdklab
2024-11-11 17:47 ` dpdklab
2024-11-11 18:15 ` |SUCCESS| " dpdklab
2024-11-11 18:32 ` dpdklab
2024-11-11 19:06 ` |WARNING| " dpdklab
2024-11-11 19:07 ` dpdklab
2024-11-11 19:21 ` |SUCCESS| " dpdklab
2024-11-11 19:28 ` dpdklab
2024-11-11 20:47 ` |WARNING| " dpdklab
2024-11-11 20:49 ` dpdklab
2024-11-11 20:53 ` |SUCCESS| " dpdklab
2024-11-11 23:02 ` 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=20241111132959.B9928123151@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@huawei.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).