From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143054 [PATCH v3] net/gve: add support for TSO in DQO RDA
Date: Sat, 10 Aug 2024 02:22:21 +0800 [thread overview]
Message-ID: <202408091822.479IMLao4164109@localhost.localdomain> (raw)
In-Reply-To: <1723229462-2439640-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143054
_Compilation OK_
Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: Fri, 9 Aug 2024 18:51:02 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b
143054 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-08-09 18:51 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1723229462-2439640-1-git-send-email-tathagat.dpdk@gmail.com>
2024-08-09 18:22 ` qemudev [this message]
2024-08-09 18:27 ` qemudev
2024-08-09 18:50 ` checkpatch
2024-08-09 20:59 ` |SUCCESS| pw143054 [PATCH] [v3] net/gve: add support for TSO in DQO dpdklab
2024-08-09 21:00 ` |PENDING| " dpdklab
2024-08-09 21:02 ` |SUCCESS| " dpdklab
2024-08-09 21:04 ` dpdklab
2024-08-09 21:11 ` dpdklab
2024-08-09 21:12 ` dpdklab
2024-08-09 21:15 ` dpdklab
2024-08-09 21:17 ` dpdklab
2024-08-09 21:23 ` dpdklab
2024-08-09 21:23 ` dpdklab
2024-08-09 21:38 ` |WARNING| " dpdklab
2024-08-09 21:43 ` |SUCCESS| " dpdklab
2024-08-09 21:46 ` dpdklab
2024-08-09 21:47 ` dpdklab
2024-08-09 21:58 ` |WARNING| " dpdklab
2024-08-09 21:59 ` dpdklab
2024-08-09 22:03 ` dpdklab
2024-08-09 22:03 ` dpdklab
2024-08-09 22:10 ` |PENDING| " dpdklab
2024-08-09 22:10 ` |WARNING| " dpdklab
2024-08-09 22:12 ` |SUCCESS| " dpdklab
2024-08-09 22:13 ` |PENDING| " dpdklab
2024-08-09 22:14 ` dpdklab
2024-08-09 22:17 ` |WARNING| " dpdklab
2024-08-09 22:17 ` |SUCCESS| " dpdklab
2024-08-09 22:18 ` dpdklab
2024-08-09 22:18 ` |WARNING| " dpdklab
2024-08-09 23:37 ` |PENDING| " dpdklab
2024-08-09 23:38 ` dpdklab
2024-08-09 23:40 ` dpdklab
2024-08-09 23:41 ` dpdklab
2024-08-09 23:43 ` dpdklab
2024-08-09 23:43 ` dpdklab
2024-08-09 23:44 ` dpdklab
2024-08-09 23:45 ` dpdklab
2024-08-09 23:45 ` dpdklab
2024-08-09 23:46 ` dpdklab
2024-08-09 23:51 ` dpdklab
2024-08-09 23:53 ` dpdklab
2024-08-09 23:53 ` dpdklab
2024-08-09 23:54 ` dpdklab
2024-08-09 23:57 ` dpdklab
2024-08-09 23:57 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-09 23:58 ` dpdklab
2024-08-10 0:02 ` dpdklab
2024-08-10 0:02 ` dpdklab
2024-08-10 0:03 ` dpdklab
2024-08-10 0:03 ` dpdklab
2024-08-10 0:03 ` dpdklab
2024-08-10 0:04 ` dpdklab
2024-08-10 0:05 ` dpdklab
2024-08-10 0:05 ` dpdklab
2024-08-10 0:05 ` dpdklab
2024-08-10 0:06 ` dpdklab
2024-08-10 0:09 ` dpdklab
2024-08-10 0:11 ` dpdklab
2024-08-10 0:12 ` dpdklab
2024-08-10 0:15 ` |SUCCESS| " dpdklab
2024-08-10 0:15 ` |PENDING| " dpdklab
2024-08-10 0:16 ` dpdklab
2024-08-10 0:17 ` dpdklab
2024-08-10 0:19 ` dpdklab
2024-08-10 0:20 ` dpdklab
2024-08-10 0:22 ` dpdklab
2024-08-10 0:23 ` dpdklab
2024-08-10 0:23 ` dpdklab
2024-08-10 0:26 ` dpdklab
2024-08-10 0:29 ` dpdklab
2024-08-10 0:31 ` dpdklab
2024-08-10 0:34 ` dpdklab
2024-08-10 0:36 ` dpdklab
2024-08-10 0:39 ` dpdklab
2024-08-10 0:40 ` dpdklab
2024-08-10 0:47 ` |SUCCESS| " dpdklab
2024-08-10 1:11 ` |PENDING| " dpdklab
2024-08-10 1:17 ` |SUCCESS| " dpdklab
2024-08-10 1:17 ` dpdklab
2024-08-10 7:28 ` dpdklab
2024-08-10 16:58 ` 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=202408091822.479IMLao4164109@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).