automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw148028 [TEST v10] ethdev: support single queue per port
Date: Wed,  6 Nov 2024 23:02:40 +0100 (CET)	[thread overview]
Message-ID: <20241106220241.18891123151@dpdk.org> (raw)
In-Reply-To: <20241106220216.1505231-1-mb@smartsharesystems.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#58: 
  587 |         dev->data->rx_queue_state[q_id] = RTE_ETH_QUEUE_STATE_STOPPED;

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#247: FILE: drivers/net/mana/tx.c:77:
+    __rte_assume(priv->num_queues < RTE_MAX_QUEUES_PER_PORT);$

CHECK:CAMELCASE: Avoid CamelCase: <ucastPktsTxOK>
#267: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1480:
+		packets = txStats.ucastPktsTxOK +

CHECK:CAMELCASE: Avoid CamelCase: <ucastBytesTxOK>
#272: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1484:
+		bytes = txStats.ucastBytesTxOK +

CHECK:CAMELCASE: Avoid CamelCase: <ucastPktsRxOK>
#292: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1501:
+		packets = rxStats.ucastPktsRxOK +

CHECK:CAMELCASE: Avoid CamelCase: <ucastBytesRxOK>
#297: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1505:
+		bytes = rxStats.ucastBytesRxOK +

CHECK:CAMELCASE: Avoid CamelCase: <pktsRxError>
#313: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1517:
+			stats->q_errors[i] = rxStats.pktsRxError;

CHECK:CAMELCASE: Avoid CamelCase: <UPT1_TxStats>
#346: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.h:124:
+	UPT1_TxStats          snapshot_tx_stats[VMXNET3_EXT_MAX_TX_QUEUES];

CHECK:CAMELCASE: Avoid CamelCase: <UPT1_RxStats>
#347: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.h:125:
+	UPT1_RxStats          snapshot_rx_stats[VMXNET3_EXT_MAX_RX_QUEUES];

total: 0 errors, 2 warnings, 227 lines checked

  parent reply	other threads:[~2024-11-06 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241106220216.1505231-1-mb@smartsharesystems.com>
2024-11-06 21:32 ` |SUCCESS| " qemudev
2024-11-06 21:36 ` |FAILURE| " qemudev
2024-11-06 22:02 ` checkpatch [this message]
2024-11-07  0:32 ` 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=20241106220241.18891123151@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).