From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129631 [PATCH v9 1/1] dts: add smoke tests
Date: Tue, 18 Jul 2023 22:46:10 +0800 [thread overview]
Message-ID: <202307181446.36IEkALO096327@localhost.localdomain> (raw)
In-Reply-To: <20230718144659.14328-4-jspewock@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129631
_Compilation OK_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tue, 18 Jul 2023 10:44:19 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 655eb37b18b1b0dc4d106acdf0dfedde01cfb224
129631 --> 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-07-18 15:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230718144659.14328-4-jspewock@iol.unh.edu>
2023-07-18 14:46 ` qemudev [this message]
2023-07-18 14:49 ` checkpatch
2023-07-18 14:50 ` qemudev
2023-07-18 15:38 ` 0-day Robot
2023-07-18 15:58 |SUCCESS| pw129631 [PATCH] [v9,1/1] " dpdklab
2023-07-18 15:59 dpdklab
2023-07-18 16:01 dpdklab
2023-07-18 16:03 dpdklab
2023-07-18 16:05 dpdklab
2023-07-18 16:05 dpdklab
2023-07-18 16:41 dpdklab
2023-07-18 16:45 dpdklab
2023-07-18 17:02 dpdklab
2023-07-18 17:02 dpdklab
2023-07-18 17:03 dpdklab
2023-07-18 17:04 dpdklab
2023-07-18 17:14 dpdklab
2023-07-18 17:19 dpdklab
2023-07-18 17:23 dpdklab
2023-07-18 17:25 dpdklab
2023-07-18 17:27 dpdklab
2023-07-18 19:01 dpdklab
2023-07-18 19:07 dpdklab
2023-07-18 19:17 dpdklab
2023-07-18 19:21 dpdklab
2023-07-18 19:26 dpdklab
2023-07-18 19:27 dpdklab
2023-07-18 19:32 dpdklab
2023-07-18 19:59 dpdklab
2023-07-18 22:45 dpdklab
2023-07-18 22:57 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=202307181446.36IEkALO096327@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).