From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138397 [PATCH] net/gve: add IPv4 checksum offloading capability
Date: Thu, 14 Mar 2024 13:19:41 +0100 (CET) [thread overview]
Message-ID: <20240314121941.E8C611223EF@dpdk.org> (raw)
In-Reply-To: <20240314121854.2551690-1-rushilg@google.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138397
_coding style OK_
next prev parent reply other threads:[~2024-03-14 12:19 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314121854.2551690-1-rushilg@google.com>
2024-03-14 11:56 ` qemudev
2024-03-14 12:01 ` qemudev
2024-03-14 12:19 ` checkpatch [this message]
2024-03-14 13:23 ` 0-day Robot
2024-03-14 17:34 ` |SUCCESS| pw138397 [PATCH] net/gve: add IPv4 checksum offloading cap dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:37 ` dpdklab
2024-03-14 17:37 ` dpdklab
2024-03-14 17:50 ` dpdklab
2024-03-14 17:53 ` dpdklab
2024-03-14 17:54 ` dpdklab
2024-03-14 17:54 ` dpdklab
2024-03-14 17:55 ` dpdklab
2024-03-14 17:56 ` dpdklab
2024-03-14 17:57 ` dpdklab
2024-03-14 17:58 ` dpdklab
2024-03-14 17:58 ` dpdklab
2024-03-14 17:59 ` dpdklab
2024-03-14 18:00 ` dpdklab
2024-03-14 18:00 ` dpdklab
2024-03-14 18:00 ` dpdklab
2024-03-14 18:02 ` dpdklab
2024-03-14 18:12 ` dpdklab
2024-03-14 18:12 ` dpdklab
2024-03-14 18:13 ` dpdklab
2024-03-14 18:14 ` dpdklab
2024-03-14 18:15 ` dpdklab
2024-03-14 18:15 ` dpdklab
2024-03-14 18:15 ` dpdklab
2024-03-14 18:15 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:19 ` dpdklab
2024-03-14 18:19 ` dpdklab
2024-03-14 18:19 ` dpdklab
2024-03-14 18:19 ` dpdklab
2024-03-14 18:19 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:21 ` dpdklab
2024-03-14 18:21 ` dpdklab
2024-03-14 18:21 ` dpdklab
2024-03-14 18:21 ` dpdklab
2024-03-14 18:22 ` dpdklab
2024-03-14 18:24 ` dpdklab
2024-03-14 18:27 ` dpdklab
2024-03-14 18:28 ` dpdklab
2024-03-14 18:29 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:31 ` dpdklab
2024-03-14 18:31 ` dpdklab
2024-03-14 18:32 ` dpdklab
2024-03-14 18:32 ` dpdklab
2024-03-14 18:33 ` dpdklab
2024-03-14 18:33 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:41 ` dpdklab
2024-03-14 18:44 ` dpdklab
2024-03-14 19:14 ` dpdklab
2024-03-18 11:43 ` dpdklab
2024-03-18 12:21 ` 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=20240314121941.E8C611223EF@dpdk.org \
--to=checkpatch@dpdk.org \
--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).