From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rushil Gupta <rushilg@google.com>
Subject: |WARNING| pw137983 [RFC] net/gve: add IPv4 checksum offloading capability
Date: Tue, 5 Mar 2024 09:41:37 +0100 (CET) [thread overview]
Message-ID: <20240305084137.B4A6B122335@dpdk.org> (raw)
In-Reply-To: <20240305084026.2329691-1-rushilg@google.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137983
_coding style issues_
ERROR:SPACING: space required before the open parenthesis '('
#184: FILE: drivers/net/gve/gve_rx_dqo.c:85:
+ if(!rx_desc->l3_l4_processed)
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 2 errors, 0 warnings, 0 checks, 124 lines checked
next prev parent reply other threads:[~2024-03-05 8:41 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305084026.2329691-1-rushilg@google.com>
2024-03-05 8:16 ` |SUCCESS| " qemudev
2024-03-05 8:21 ` qemudev
2024-03-05 8:41 ` checkpatch [this message]
2024-03-05 9:45 ` 0-day Robot
2024-03-05 9:46 ` |SUCCESS| pw137983 [PATCH] [RFC] net/gve: add IPv4 checksum offloadi dpdklab
2024-03-05 9:46 ` dpdklab
2024-03-05 9:47 ` dpdklab
2024-03-05 9:47 ` dpdklab
2024-03-05 9:52 ` dpdklab
2024-03-05 9:52 ` dpdklab
2024-03-05 9:53 ` dpdklab
2024-03-05 9:53 ` dpdklab
2024-03-05 9:54 ` dpdklab
2024-03-05 9:54 ` dpdklab
2024-03-05 9:54 ` dpdklab
2024-03-05 9:55 ` dpdklab
2024-03-05 9:55 ` dpdklab
2024-03-05 9:55 ` dpdklab
2024-03-05 9:55 ` dpdklab
2024-03-05 9:56 ` dpdklab
2024-03-05 9:56 ` dpdklab
2024-03-05 9:56 ` dpdklab
2024-03-05 9:56 ` dpdklab
2024-03-05 9:57 ` dpdklab
2024-03-05 9:57 ` dpdklab
2024-03-05 9:57 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:58 ` dpdklab
2024-03-05 9:59 ` dpdklab
2024-03-05 9:59 ` dpdklab
2024-03-05 9:59 ` dpdklab
2024-03-05 9:59 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:00 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:01 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:02 ` dpdklab
2024-03-05 10:03 ` dpdklab
2024-03-05 10:04 ` dpdklab
2024-03-05 10:05 ` dpdklab
2024-03-05 10:05 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:07 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:08 ` dpdklab
2024-03-05 10:09 ` dpdklab
2024-03-05 10:12 ` dpdklab
2024-03-05 10:13 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 10:26 ` dpdklab
2024-03-05 11:10 ` dpdklab
2024-03-08 22:20 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 23:25 ` 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=20240305084137.B4A6B122335@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).