automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ronak Doshi <ronak.doshi@broadcom.com>
Subject: |WARNING| pw155122 [PATCH net] net/vmxnet3: fix mapping of mempools to queues
Date: Wed,  9 Jul 2025 23:46:45 +0200 (CEST)	[thread overview]
Message-ID: <20250709214646.112C91252F5@dpdk.org> (raw)
In-Reply-To: <20250709212905.126851-1-ronak.doshi@broadcom.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155122

_coding style issues_


CHECK:CAMELCASE: Avoid CamelCase: <txQueueBits>
#159: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:865:
+		mr->txQueueBits = index[i] & tx_index_mask;

CHECK:CAMELCASE: Avoid CamelCase: <startPA>
#166: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:870:
+			     j, mr->startPA, mr->length,

CHECK:CAMELCASE: Avoid CamelCase: <rxQueueBits>
#167: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:871:
+			     mr->rxQueueBits, mr->txQueueBits);

total: 0 errors, 0 warnings, 3 checks, 65 lines checked

  parent reply	other threads:[~2025-07-09 21:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250709212905.126851-1-ronak.doshi@broadcom.com>
2025-07-09 21:13 ` |SUCCESS| " qemudev
2025-07-09 21:17 ` qemudev
2025-07-09 21:46 ` checkpatch [this message]
2025-07-09 23:04 ` 0-day Robot
2025-07-10  1:17 ` |SUCCESS| pw155122 [PATCH] [net] net/vmxnet3: fix mapping of mempool dpdklab
2025-07-10  1:24 ` dpdklab
2025-07-10  1:25 ` dpdklab
2025-07-10  1:36 ` dpdklab
2025-07-10  1:42 ` dpdklab
2025-07-10  1:56 ` |PENDING| " dpdklab
2025-07-10  2:00 ` dpdklab
2025-07-10  2:02 ` dpdklab
2025-07-10  2:10 ` |SUCCESS| " dpdklab
2025-07-10  2:34 ` dpdklab
2025-07-10  2:39 ` dpdklab
2025-07-10  2:45 ` |WARNING| " dpdklab
2025-07-10  3:21 ` dpdklab
2025-07-10  3:24 ` |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=20250709214646.112C91252F5@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=ronak.doshi@broadcom.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).