From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126904 [PATCH v2] net/e1000/base: add new devices
Date: Wed, 17 May 2023 14:58:28 +0800 [thread overview]
Message-ID: <202305170658.34H6wSwM1161949@localhost.localdomain> (raw)
In-Reply-To: <20230517064453.1079653-1-qiming.yang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126904
_Compilation OK_
Submitter: Qiming Yang <qiming.yang@intel.com>
Date: Wed, 17 May 2023 06:44:53 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: df266e57d85d80e4ad69e9dd3271a16cc9145d79
126904 --> 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-05-17 7:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230517064453.1079653-1-qiming.yang@intel.com>
2023-05-17 6:58 ` qemudev [this message]
2023-05-17 7:02 ` qemudev
2023-05-17 7:02 ` checkpatch
2023-05-17 7:40 ` |FAILURE| " 0-day Robot
2023-05-17 14:40 |SUCCESS| pw126904 [PATCH] [v2] " dpdklab
2023-05-17 14:42 dpdklab
2023-05-17 14:47 dpdklab
2023-05-17 14:47 dpdklab
2023-05-17 14:48 dpdklab
2023-05-17 14:54 dpdklab
2023-05-17 14:55 dpdklab
2023-05-17 14:58 dpdklab
2023-05-17 15:03 dpdklab
2023-05-17 15:07 dpdklab
2023-05-17 15:08 dpdklab
2023-05-17 15:13 dpdklab
2023-05-17 15:22 dpdklab
2023-05-17 15:55 dpdklab
2023-05-17 16:00 dpdklab
2023-05-17 16:04 dpdklab
2023-05-17 16:13 dpdklab
2023-05-17 16:13 dpdklab
2023-05-17 16:18 dpdklab
2023-05-17 16:27 dpdklab
2023-05-17 16:32 dpdklab
2023-05-17 16:33 dpdklab
2023-05-17 16:35 dpdklab
2023-05-17 19:03 dpdklab
2023-05-17 20:06 dpdklab
2023-05-17 21:16 dpdklab
2023-05-17 21:16 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=202305170658.34H6wSwM1161949@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).