From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Subject: |WARNING| pw142820 [PATCH] net/gve: Add support for TSO in DQO RDA
Date: Thu, 1 Aug 2024 12:18:51 +0200 (CEST) [thread overview]
Message-ID: <20240801101851.C0DBD123EF2@dpdk.org> (raw)
In-Reply-To: <1722507548-2401507-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142820
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#99: FILE: drivers/net/gve/gve_tx_dqo.c:78:
+ uint32_t hlen = tx_pkt->l2_len + tx_pkt->l3_len + tx_pkt->l4_len;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#100: FILE: drivers/net/gve/gve_tx_dqo.c:79:
+ desc->tso_ctx.cmd_dtype.dtype = GVE_TX_TSO_CTX_DESC_DTYPE_DQO;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#101: FILE: drivers/net/gve/gve_tx_dqo.c:80:
+ desc->tso_ctx.cmd_dtype.tso = 1;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#102: FILE: drivers/net/gve/gve_tx_dqo.c:81:
+ desc->tso_ctx.mss = (uint16_t)tx_pkt->tso_segsz;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#103: FILE: drivers/net/gve/gve_tx_dqo.c:82:
+ desc->tso_ctx.tso_total_len = tx_pkt->pkt_len - hlen;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#104: FILE: drivers/net/gve/gve_tx_dqo.c:83:
+ desc->tso_ctx.header_len = (uint8_t)hlen;$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#150: FILE: drivers/net/gve/gve_tx_dqo.c:148:
+^I^I$
total: 1 errors, 6 warnings, 0 checks, 75 lines checked
next prev parent reply other threads:[~2024-08-01 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722507548-2401507-1-git-send-email-tathagat.dpdk@gmail.com>
2024-08-01 9:57 ` qemudev
2024-08-01 10:18 ` checkpatch [this message]
2024-08-01 19:56 ` 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=20240801101851.C0DBD123EF2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=tathagat.dpdk@gmail.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).