From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142858 [PATCH v5] net/gve : Update EOP & csum bit in txd rte_mbuf chain
Date: Fri, 2 Aug 2024 07:07:04 +0200 (CEST) [thread overview]
Message-ID: <20240802050704.4478E123EF2@dpdk.org> (raw)
In-Reply-To: <1722575288-2408630-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142858
_coding style OK_
next prev parent reply other threads:[~2024-08-02 5:07 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722575288-2408630-1-git-send-email-tathagat.dpdk@gmail.com>
2024-08-02 4:39 ` qemudev
2024-08-02 4:43 ` qemudev
2024-08-02 5:07 ` checkpatch [this message]
2024-08-02 6:02 ` 0-day Robot
2024-08-02 6:55 ` |SUCCESS| pw142858 [PATCH] [v5] net/gve : Update EOP & csum bit in t dpdklab
2024-08-02 7:07 ` |PENDING| " dpdklab
2024-08-02 7:20 ` |SUCCESS| " dpdklab
2024-08-02 7:23 ` |PENDING| " dpdklab
2024-08-02 7:34 ` dpdklab
2024-08-02 7:36 ` |SUCCESS| " dpdklab
2024-08-02 7:45 ` |PENDING| " dpdklab
2024-08-02 7:46 ` dpdklab
2024-08-02 7:50 ` dpdklab
2024-08-02 7:58 ` dpdklab
2024-08-02 8:03 ` dpdklab
2024-08-02 8:04 ` dpdklab
2024-08-02 8:05 ` dpdklab
2024-08-02 8:07 ` dpdklab
2024-08-02 8:08 ` dpdklab
2024-08-02 8:12 ` dpdklab
2024-08-02 8:14 ` dpdklab
2024-08-02 8:17 ` dpdklab
2024-08-02 8:18 ` |SUCCESS| " dpdklab
2024-08-02 8:24 ` dpdklab
2024-08-02 10:02 ` |PENDING| " dpdklab
2024-08-02 10:11 ` |SUCCESS| " dpdklab
2024-08-02 10:46 ` dpdklab
2024-08-02 12:14 ` |PENDING| " dpdklab
2024-08-02 12:16 ` dpdklab
2024-08-02 12:18 ` dpdklab
2024-08-02 12:22 ` dpdklab
2024-08-02 12:35 ` |SUCCESS| " dpdklab
2024-08-02 12:36 ` |PENDING| " dpdklab
2024-08-02 12:36 ` dpdklab
2024-08-02 12:40 ` dpdklab
2024-08-02 12:40 ` |SUCCESS| " dpdklab
2024-08-02 12:41 ` |PENDING| " dpdklab
2024-08-02 12:41 ` dpdklab
2024-08-02 12:43 ` dpdklab
2024-08-02 12:45 ` dpdklab
2024-08-02 12:45 ` |SUCCESS| " dpdklab
2024-08-02 12:46 ` |PENDING| " dpdklab
2024-08-02 12:47 ` dpdklab
2024-08-02 12:50 ` |SUCCESS| " dpdklab
2024-08-02 12:53 ` |PENDING| " dpdklab
2024-08-02 12:54 ` dpdklab
2024-08-02 12:57 ` dpdklab
2024-08-02 12:59 ` dpdklab
2024-08-02 12:59 ` dpdklab
2024-08-02 13:01 ` dpdklab
2024-08-02 13:01 ` dpdklab
2024-08-02 13:02 ` dpdklab
2024-08-02 13:03 ` dpdklab
2024-08-02 13:03 ` dpdklab
2024-08-02 13:05 ` dpdklab
2024-08-02 13:06 ` dpdklab
2024-08-02 13:07 ` dpdklab
2024-08-02 13:08 ` dpdklab
2024-08-02 13:08 ` dpdklab
2024-08-02 13:09 ` |SUCCESS| " dpdklab
2024-08-02 13:10 ` |PENDING| " dpdklab
2024-08-02 13:10 ` dpdklab
2024-08-02 13:11 ` dpdklab
2024-08-02 13:12 ` dpdklab
2024-08-02 13:12 ` dpdklab
2024-08-02 13:14 ` dpdklab
2024-08-02 13:15 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:19 ` dpdklab
2024-08-02 13:22 ` dpdklab
2024-08-02 13:22 ` dpdklab
2024-08-02 13:24 ` dpdklab
2024-08-02 13:25 ` dpdklab
2024-08-02 13:29 ` dpdklab
2024-08-02 13:29 ` dpdklab
2024-08-02 13:30 ` dpdklab
2024-08-02 13:31 ` dpdklab
2024-08-02 13:34 ` dpdklab
2024-08-02 13:35 ` dpdklab
2024-08-02 13:35 ` dpdklab
2024-08-02 13:36 ` dpdklab
2024-08-02 13:37 ` dpdklab
2024-08-02 13:38 ` dpdklab
2024-08-02 13:39 ` dpdklab
2024-08-02 13:39 ` dpdklab
2024-08-02 13:40 ` dpdklab
2024-08-02 13:43 ` dpdklab
2024-08-02 13:43 ` |SUCCESS| " dpdklab
2024-08-02 13:44 ` |PENDING| " dpdklab
2024-08-02 13:50 ` dpdklab
2024-08-02 13:54 ` dpdklab
2024-08-02 13:56 ` dpdklab
2024-08-02 13:58 ` dpdklab
2024-08-02 13:59 ` dpdklab
2024-08-02 14:00 ` dpdklab
2024-08-02 14:03 ` dpdklab
2024-08-02 14:04 ` dpdklab
2024-08-02 14:04 ` dpdklab
2024-08-02 14:06 ` dpdklab
2024-08-02 14:08 ` |SUCCESS| " dpdklab
2024-08-02 14:08 ` dpdklab
2024-08-02 14:09 ` dpdklab
2024-08-02 14:09 ` dpdklab
2024-08-02 14:17 ` dpdklab
2024-08-03 8:46 ` dpdklab
2024-08-06 11:21 ` dpdklab
2024-08-06 11:30 ` dpdklab
2024-08-06 11:43 ` 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=20240802050704.4478E123EF2@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).