From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw134428 [PATCH v3] net/axgbe: support TSO
Date: Thu, 16 Nov 2023 23:45:30 +0800 [thread overview]
Message-ID: <202311161545.3AGFjUY1143182@localhost.localdomain> (raw)
In-Reply-To: <20231116160326.76189-1-jesna.k.e@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/134428
_Compilation OK_
Submitter: Jesna K E <jesna.k.e@amd.com>
Date: Thu, 16 Nov 2023 21:33:26 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 92d7ce4afc4a558f27bbc8368823c625f4e0f9dc
134428 --> 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:[~2023-11-16 16:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231116160326.76189-1-jesna.k.e@amd.com>
2023-11-16 15:45 ` qemudev [this message]
2023-11-16 15:49 ` qemudev
2023-11-16 16:05 ` checkpatch
2023-11-16 16:59 ` 0-day Robot
2023-11-17 7:04 |SUCCESS| pw134428 [PATCH] [v3] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 6:44 dpdklab
2023-11-16 20:55 dpdklab
2023-11-16 19:30 dpdklab
2023-11-16 17:10 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:03 dpdklab
2023-11-16 17:02 dpdklab
2023-11-16 17:02 dpdklab
2023-11-16 17:01 dpdklab
2023-11-16 17:01 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 17:00 dpdklab
2023-11-16 16:59 dpdklab
2023-11-16 16:55 dpdklab
2023-11-16 16:51 dpdklab
2023-11-16 16:51 dpdklab
2023-11-16 16:49 dpdklab
2023-11-16 16:49 dpdklab
2023-11-16 16:48 dpdklab
2023-11-16 16:47 dpdklab
2023-11-16 16:47 dpdklab
2023-11-16 16:45 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:44 dpdklab
2023-11-16 16:43 dpdklab
2023-11-16 16:42 dpdklab
2023-11-16 16:38 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:37 dpdklab
2023-11-16 16:36 dpdklab
2023-11-16 16:35 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 dpdklab
2023-11-16 16:34 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=202311161545.3AGFjUY1143182@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).