From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |WARNING| pw144444 [PATCH] app/test: refactor cryptodev test cases
Date: Wed, 25 Sep 2024 21:31:37 +0200 (CEST) [thread overview]
Message-ID: <20240925193137.404CC121D9E@dpdk.org> (raw)
In-Reply-To: <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144444
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#75:
if this feature were not present, the test should not even reach this stage.
WARNING:TYPO_SPELLING: 'responsbile' may be misspelled - perhaps 'responsible'?
#1018: FILE: app/test/test_cryptodev.c:1242:
+ * This functions are responsbile for construction/destruction of individual unit test context.
total: 0 errors, 2 warnings, 3020 lines checked
next prev parent reply other threads:[~2024-09-25 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>
2024-09-25 19:03 ` |SUCCESS| " qemudev
2024-09-25 19:08 ` qemudev
2024-09-25 19:31 ` checkpatch [this message]
2024-09-25 20:23 ` 0-day Robot
2024-09-26 3:26 ` |FAILURE| " dpdklab
2024-09-26 3:28 ` |SUCCESS| " dpdklab
2024-09-26 3:33 ` dpdklab
2024-09-26 3:33 ` dpdklab
2024-09-26 3:39 ` |FAILURE| " dpdklab
2024-09-26 3:43 ` |SUCCESS| " dpdklab
2024-09-26 3:45 ` dpdklab
2024-09-26 3:50 ` dpdklab
2024-09-26 3:55 ` dpdklab
2024-09-26 4:04 ` dpdklab
2024-09-26 4:39 ` dpdklab
2024-09-26 4:58 ` |PENDING| " dpdklab
2024-09-26 5:55 ` dpdklab
2024-09-26 7:48 ` |SUCCESS| " dpdklab
2024-09-26 8:00 ` dpdklab
2024-09-26 8:14 ` dpdklab
2024-09-26 8:39 ` dpdklab
2024-09-26 12:23 ` 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=20240925193137.404CC121D9E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arkadiuszx.kusztal@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).