From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw154412 [PATCH v4] event/cnxk: add event vector adapter support
Date: Thu, 12 Jun 2025 19:09:03 +0200 (CEST) [thread overview]
Message-ID: <20250612170903.637B81252C1@dpdk.org> (raw)
In-Reply-To: <20250612170923.36114-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154412
_coding style issues_
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#334: 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, 230 lines checked
next prev parent reply other threads:[~2025-06-12 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612170923.36114-1-pbhagavatula@marvell.com>
2025-06-12 16:35 ` |SUCCESS| " qemudev
2025-06-12 16:39 ` qemudev
2025-06-12 17:09 ` checkpatch [this message]
2025-06-12 18:05 ` |SUCCESS| pw154412 [PATCH] [v4] event/cnxk: add event vector adapter dpdklab
2025-06-12 18:15 ` |PENDING| " dpdklab
2025-06-12 18:16 ` |SUCCESS| " dpdklab
2025-06-12 18:17 ` dpdklab
2025-06-12 18:27 ` |SUCCESS| pw154412 [PATCH v4] event/cnxk: add event vector adapter support 0-day Robot
2025-06-12 18:28 ` |SUCCESS| pw154412 [PATCH] [v4] event/cnxk: add event vector adapter dpdklab
2025-06-12 18:33 ` |PENDING| " dpdklab
2025-06-12 18:40 ` |SUCCESS| " dpdklab
2025-06-12 18:58 ` dpdklab
2025-06-12 19:03 ` dpdklab
2025-06-12 19:10 ` |PENDING| " dpdklab
2025-06-12 19:17 ` dpdklab
2025-06-12 19:40 ` |SUCCESS| " dpdklab
2025-06-12 19:52 ` dpdklab
2025-06-12 20:45 ` dpdklab
2025-06-12 23:28 ` |PENDING| " dpdklab
2025-06-13 4:20 ` |SUCCESS| " dpdklab
2025-06-13 7:39 ` dpdklab
2025-06-13 7:41 ` dpdklab
2025-06-13 15:10 ` |WARNING| " 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=20250612170903.637B81252C1@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).