From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw147229 [PATCH v2] net/vmxnet3: support per-queue stats for fewer queues
Date: Fri, 25 Oct 2024 11:28:31 +0200 (CEST) [thread overview]
Message-ID: <20241025092831.A8306123108@dpdk.org> (raw)
In-Reply-To: <20241025092734.1222248-1-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/147229
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <ucastPktsTxOK>
#87: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1480:
+ packets = txStats.ucastPktsTxOK +
CHECK:CAMELCASE: Avoid CamelCase: <ucastBytesTxOK>
#92: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1484:
+ bytes = txStats.ucastBytesTxOK +
CHECK:CAMELCASE: Avoid CamelCase: <ucastPktsRxOK>
#112: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1501:
+ packets = rxStats.ucastPktsRxOK +
CHECK:CAMELCASE: Avoid CamelCase: <ucastBytesRxOK>
#117: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1505:
+ bytes = rxStats.ucastBytesRxOK +
CHECK:CAMELCASE: Avoid CamelCase: <pktsRxError>
#133: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1517:
+ stats->q_errors[i] = rxStats.pktsRxError;
CHECK:CAMELCASE: Avoid CamelCase: <UPT1_TxStats>
#166: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.h:124:
+ UPT1_TxStats snapshot_tx_stats[VMXNET3_EXT_MAX_TX_QUEUES];
CHECK:CAMELCASE: Avoid CamelCase: <UPT1_RxStats>
#167: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.h:125:
+ UPT1_RxStats snapshot_rx_stats[VMXNET3_EXT_MAX_RX_QUEUES];
total: 0 errors, 0 warnings, 7 checks, 88 lines checked
next prev parent reply other threads:[~2024-10-25 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241025092734.1222248-1-mb@smartsharesystems.com>
2024-10-25 8:57 ` |SUCCESS| " qemudev
2024-10-25 9:01 ` qemudev
2024-10-25 9:28 ` checkpatch [this message]
2024-10-25 10:29 ` 0-day Robot
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=20241025092831.A8306123108@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mb@smartsharesystems.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).