From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kommula Shiva Shankar <kshankar@marvell.com>
Subject: |WARNING| pw150538 [PATCH] net/virtio: add virtio hash report feature
Date: Sun, 26 Jan 2025 20:34:44 +0100 (CET) [thread overview]
Message-ID: <20250126193444.BE8BE127001@dpdk.org> (raw)
In-Reply-To: <20250126193404.3431544-1-kshankar@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150538
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_IPv4>
#268: FILE: drivers/net/virtio/virtqueue.h:268:
+#define VIRTIO_NET_HASH_REPORT_IPv4 1
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_TCPv4>
#269: FILE: drivers/net/virtio/virtqueue.h:269:
+#define VIRTIO_NET_HASH_REPORT_TCPv4 2
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_UDPv4>
#270: FILE: drivers/net/virtio/virtqueue.h:270:
+#define VIRTIO_NET_HASH_REPORT_UDPv4 3
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_IPv6>
#271: FILE: drivers/net/virtio/virtqueue.h:271:
+#define VIRTIO_NET_HASH_REPORT_IPv6 4
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_TCPv6>
#272: FILE: drivers/net/virtio/virtqueue.h:272:
+#define VIRTIO_NET_HASH_REPORT_TCPv6 5
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_UDPv6>
#273: FILE: drivers/net/virtio/virtqueue.h:273:
+#define VIRTIO_NET_HASH_REPORT_UDPv6 6
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_IPv6_EX>
#274: FILE: drivers/net/virtio/virtqueue.h:274:
+#define VIRTIO_NET_HASH_REPORT_IPv6_EX 7
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_TCPv6_EX>
#275: FILE: drivers/net/virtio/virtqueue.h:275:
+#define VIRTIO_NET_HASH_REPORT_TCPv6_EX 8
CHECK:CAMELCASE: Avoid CamelCase: <VIRTIO_NET_HASH_REPORT_UDPv6_EX>
#276: FILE: drivers/net/virtio/virtqueue.h:276:
+#define VIRTIO_NET_HASH_REPORT_UDPv6_EX 9
total: 0 errors, 0 warnings, 9 checks, 159 lines checked
next prev parent reply other threads:[~2025-01-26 19:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250126193404.3431544-1-kshankar@marvell.com>
2025-01-26 19:07 ` |SUCCESS| " qemudev
2025-01-26 19:11 ` qemudev
2025-01-26 19:34 ` checkpatch [this message]
2025-01-26 20:12 ` |PENDING| pw150538 [PATCH] net/virtio: add virtio hash report featur dpdklab
2025-01-26 20:15 ` |SUCCESS| " dpdklab
2025-01-26 20:19 ` |PENDING| " dpdklab
2025-01-26 20:20 ` |SUCCESS| " dpdklab
2025-01-26 20:23 ` |SUCCESS| pw150538 [PATCH] net/virtio: add virtio hash report feature 0-day Robot
2025-01-26 20:26 ` |PENDING| pw150538 [PATCH] net/virtio: add virtio hash report featur dpdklab
2025-01-26 20:29 ` dpdklab
2025-01-26 20:30 ` |SUCCESS| " dpdklab
2025-01-26 20:31 ` dpdklab
2025-01-26 20:35 ` |PENDING| " dpdklab
2025-01-26 20:37 ` |SUCCESS| " dpdklab
2025-01-26 20:37 ` dpdklab
2025-01-26 20:49 ` dpdklab
2025-01-26 21:15 ` dpdklab
2025-01-26 21:17 ` dpdklab
2025-01-26 21:21 ` dpdklab
2025-01-26 21:31 ` dpdklab
2025-01-26 21:48 ` |WARNING| " dpdklab
2025-01-26 22:05 ` |SUCCESS| " 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=20250126193444.BE8BE127001@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kshankar@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).