From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw138644 [PATCH 2/2] eal: add rte ffs32 and rte ffs64 inline functions
Date: Wed, 20 Mar 2024 22:26:03 +0100 (CET) [thread overview]
Message-ID: <20240320212603.53A201223F9@dpdk.org> (raw)
In-Reply-To: <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138644
_coding style issues_
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#76: FILE: lib/eal/include/rte_bitops.h:413:
+ if (0 == _BitScanForward(&rv, v))
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#87: FILE: lib/eal/include/rte_bitops.h:424:
+ if (0 == _BitScanForward64(&rv, v))
total: 0 errors, 2 warnings, 46 lines checked
next prev parent reply other threads:[~2024-03-20 21:26 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 21:23 ` |SUCCESS| pw138645-138644 " qemudev
2024-03-20 21:26 ` checkpatch [this message]
2024-03-20 21:27 ` qemudev
2024-03-20 22:24 ` |SUCCESS| pw138644 " 0-day Robot
2024-03-21 2:18 ` |SUCCESS| pw138645-138644 [PATCH] [2/2] eal: add rte ffs32 and rte f dpdklab
2024-03-21 2:18 ` dpdklab
2024-03-21 2:19 ` dpdklab
2024-03-21 2:20 ` dpdklab
2024-03-21 2:20 ` dpdklab
2024-03-21 2:21 ` dpdklab
2024-03-21 2:21 ` dpdklab
2024-03-21 2:23 ` dpdklab
2024-03-21 2:24 ` dpdklab
2024-03-21 2:25 ` dpdklab
2024-03-21 2:26 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:31 ` dpdklab
2024-03-21 2:35 ` dpdklab
2024-03-21 2:39 ` dpdklab
2024-03-21 2:57 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:08 ` dpdklab
2024-03-21 3:11 ` dpdklab
2024-03-21 3:11 ` dpdklab
2024-03-21 3:19 ` dpdklab
2024-03-21 3:32 ` dpdklab
2024-03-21 3:44 ` dpdklab
2024-03-21 3:44 ` dpdklab
2024-03-21 3:46 ` dpdklab
2024-03-21 3:46 ` dpdklab
2024-03-21 3:47 ` dpdklab
2024-03-21 4:39 ` dpdklab
2024-03-21 5:23 ` dpdklab
2024-03-21 5:41 ` dpdklab
2024-03-21 5:55 ` dpdklab
2024-03-21 5:55 ` dpdklab
2024-03-21 5:57 ` dpdklab
2024-03-21 5:58 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 6:00 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:07 ` dpdklab
2024-03-21 6:12 ` dpdklab
2024-03-21 6:12 ` dpdklab
2024-03-21 6:13 ` dpdklab
2024-03-21 6:13 ` dpdklab
2024-03-21 6:15 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:18 ` dpdklab
2024-03-21 6:20 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:34 ` dpdklab
2024-03-21 6:36 ` dpdklab
2024-03-21 7:55 ` dpdklab
2024-03-21 9:18 ` dpdklab
2024-03-21 10:58 ` dpdklab
2024-03-21 11:40 ` dpdklab
2024-03-21 18:09 ` dpdklab
2024-03-22 19:28 ` dpdklab
2024-03-22 20: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=20240320212603.53A201223F9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roretzla@linux.microsoft.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).