From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120475 [PATCH v5] mbuf perf test, please ignore
Date: Fri, 9 Dec 2022 01:10:49 +0800 [thread overview]
Message-ID: <202212081710.2B8HAnFj200170@localhost.localdomain> (raw)
In-Reply-To: <20221206092021.60797-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120475
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Tue, 6 Dec 2022 10:20:21 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd
120475 --> 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:[~2022-12-12 11:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221206092021.60797-1-mb@smartsharesystems.com>
2022-12-06 9:20 ` checkpatch
2022-12-06 10:38 ` |FAILURE| " 0-day Robot
2022-12-08 16:34 ` |SUCCESS| " qemudev
2022-12-08 16:35 ` qemudev
2022-12-08 17:10 ` qemudev [this message]
2022-12-08 17:11 ` qemudev
2022-12-10 0:59 ` qemudev
2022-12-10 1:00 ` qemudev
2022-12-06 18:54 |SUCCESS| pw120475 [PATCH] [v5] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 13:54 dpdklab
2022-12-06 13:54 dpdklab
2022-12-06 13:34 dpdklab
2022-12-06 13:22 dpdklab
2022-12-06 13:22 dpdklab
2022-12-06 13:21 dpdklab
2022-12-06 13:21 dpdklab
2022-12-06 13:16 dpdklab
2022-12-06 12:53 dpdklab
2022-12-06 12:52 dpdklab
2022-12-06 12:51 dpdklab
2022-12-06 12:43 dpdklab
2022-12-06 12:01 dpdklab
2022-12-06 11:05 dpdklab
2022-12-06 10:52 dpdklab
2022-12-06 10:45 dpdklab
2022-12-06 10:44 dpdklab
2022-12-06 10:23 dpdklab
2022-12-06 10:14 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=202212081710.2B8HAnFj200170@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).