From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121765-121764 [PATCH v2 2/2] usertools: add an argument for file prefix
Date: Tue, 10 Jan 2023 15:34:46 +0800 [thread overview]
Message-ID: <202301100734.30A7YkQ41652182@localhost.localdomain> (raw)
In-Reply-To: <20230110073146.8221-3-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121764
_Compilation OK_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tue, 10 Jan 2023 15:31:45 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872
121765-121764 --> 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 prev parent reply other threads:[~2023-01-10 7:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230110073146.8221-3-lihuisong@huawei.com>
2023-01-10 7:33 ` |SUCCESS| pw121764 " checkpatch
2023-01-10 7:34 ` qemudev [this message]
2023-01-10 7:38 ` |SUCCESS| pw121765-121764 " qemudev
2023-01-10 8:40 ` |FAILURE| pw121764 " 0-day Robot
2023-01-10 10:02 |SUCCESS| pw121765-121764 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 10:02 dpdklab
2023-01-10 10:00 dpdklab
2023-01-10 9:59 dpdklab
2023-01-10 9:57 dpdklab
2023-01-10 9:56 dpdklab
2023-01-10 9:55 dpdklab
2023-01-10 9:54 dpdklab
2023-01-10 9:53 dpdklab
2023-01-10 9:51 dpdklab
2023-01-10 9:45 dpdklab
2023-01-10 9:45 dpdklab
2023-01-10 9:35 dpdklab
2023-01-10 9:34 dpdklab
2023-01-10 9:24 dpdklab
2023-01-10 8:48 dpdklab
2023-01-10 8:26 dpdklab
2023-01-10 8:21 dpdklab
2023-01-10 8:17 dpdklab
2023-01-10 8:10 dpdklab
2023-01-10 8:09 dpdklab
2023-01-10 8:07 dpdklab
2023-01-10 8:07 dpdklab
2023-01-10 8:02 dpdklab
2023-01-10 8:01 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=202301100734.30A7YkQ41652182@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).