From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rushil Gupta <rushilg@google.com>
Subject: |WARNING| pw135504 [PATCH] net/gve: Enable stats reporting for GQ format
Date: Fri, 22 Dec 2023 16:06:23 +0100 (CET) [thread overview]
Message-ID: <20231222150623.0CDC712485B@dpdk.org> (raw)
In-Reply-To: <20231222150553.2695916-1-rushilg@google.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135504
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#119: FILE: drivers/net/gve/gve_ethdev.c:129:
+ uint16_t nb_tx_queues, uint16_t nb_rx_queues)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#119: FILE: drivers/net/gve/gve_ethdev.c:129:
+ uint16_t nb_tx_queues, uint16_t nb_rx_queues)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#153: FILE: drivers/net/gve/gve_ethdev.c:163:
+ struct gve_priv *priv = dev->data->dev_private;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#153: FILE: drivers/net/gve/gve_ethdev.c:163:
+ struct gve_priv *priv = dev->data->dev_private;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#154: FILE: drivers/net/gve/gve_ethdev.c:164:
+ rte_memzone_free(priv->stats_report_mem);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#154: FILE: drivers/net/gve/gve_ethdev.c:164:
+ rte_memzone_free(priv->stats_report_mem);$
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#202: FILE: drivers/net/gve/gve_ethdev.c:260:
+ if (gve_is_gqi(priv))
+ {
total: 4 errors, 3 warnings, 0 checks, 257 lines checked
next prev parent reply other threads:[~2023-12-22 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231222150553.2695916-1-rushilg@google.com>
2023-12-22 14:46 ` |SUCCESS| " qemudev
2023-12-22 14:50 ` qemudev
2023-12-22 15:06 ` checkpatch [this message]
2023-12-22 16:04 ` 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=20231222150623.0CDC712485B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rushilg@google.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).