From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw154448 [PATCH v5] event/cnxk: add event vector adapter support
Date: Sat, 14 Jun 2025 01:20:29 +0200 (CEST) [thread overview]
Message-ID: <20250613232029.EDE541252C7@dpdk.org> (raw)
In-Reply-To: <20250613231942.35167-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154448
_coding style issues_
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#381: FILE: drivers/event/cnxk/cnxk_vector_adptr.c:138:
+ SSO_AGGR_MAX_CTX > UINT8_MAX ? UINT8_MAX : SSO_AGGR_MAX_CTX;
total: 0 errors, 1 warnings, 257 lines checked
next prev parent reply other threads:[~2025-06-13 23:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250613231942.35167-1-pbhagavatula@marvell.com>
2025-06-13 22:47 ` |SUCCESS| " qemudev
2025-06-13 22:51 ` qemudev
2025-06-13 23:20 ` checkpatch [this message]
2025-06-13 23:46 ` |PENDING| pw154448 [PATCH] [v5] event/cnxk: add event vector adapter dpdklab
2025-06-13 23:49 ` |SUCCESS| " dpdklab
2025-06-13 23:56 ` dpdklab
2025-06-13 23:58 ` |PENDING| " dpdklab
2025-06-14 0:02 ` |FAILURE| " dpdklab
2025-06-14 0:03 ` dpdklab
2025-06-14 0:04 ` |SUCCESS| " dpdklab
2025-06-14 0:05 ` |PENDING| " dpdklab
2025-06-14 0:06 ` |SUCCESS| " dpdklab
2025-06-14 0:26 ` |PENDING| " dpdklab
2025-06-14 0:30 ` |SUCCESS| " dpdklab
2025-06-14 0:33 ` dpdklab
2025-06-14 0:57 ` dpdklab
2025-06-14 1:07 ` dpdklab
2025-06-14 1:52 ` |FAILURE| " dpdklab
2025-06-14 1:52 ` |SUCCESS| " dpdklab
2025-06-14 1:53 ` dpdklab
2025-06-14 1:53 ` |FAILURE| " dpdklab
2025-06-14 1:53 ` |SUCCESS| " dpdklab
2025-06-14 1:53 ` |FAILURE| " dpdklab
2025-06-14 2:44 ` |SUCCESS| pw154448 [PATCH v5] event/cnxk: add event vector adapter support 0-day Robot
2025-06-14 3:10 ` |SUCCESS| pw154448 [PATCH] [v5] event/cnxk: add event vector adapter 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=20250613232029.EDE541252C7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@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).