From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138811 [PATCH v2] graph: avoid id collisions
Date: Tue, 26 Mar 2024 23:27:05 +0800 [thread overview]
Message-ID: <202403261527.42QFR5kk2894926@localhost.localdomain> (raw)
In-Reply-To: <20240326154936.1132201-1-rjarry@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138811
_Compilation OK_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tue, 26 Mar 2024 16:49:36 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ded4d4765171b88470e59307f10625e942f22fca
138811 --> 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:[~2024-03-26 15:52 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326154936.1132201-1-rjarry@redhat.com>
2024-03-26 15:27 ` qemudev [this message]
2024-03-26 15:31 ` qemudev
2024-03-26 15:51 ` |WARNING| " checkpatch
2024-03-26 16:28 ` |SUCCESS| pw138811 [PATCH] [v2] " dpdklab
2024-03-26 16:29 ` dpdklab
2024-03-26 16:30 ` dpdklab
2024-03-26 16:30 ` dpdklab
2024-03-26 16:31 ` dpdklab
2024-03-26 16:31 ` dpdklab
2024-03-26 16:31 ` dpdklab
2024-03-26 16:32 ` dpdklab
2024-03-26 16:33 ` dpdklab
2024-03-26 16:33 ` dpdklab
2024-03-26 16:34 ` dpdklab
2024-03-26 16:34 ` dpdklab
2024-03-26 16:34 ` dpdklab
2024-03-26 16:35 ` dpdklab
2024-03-26 16:36 ` dpdklab
2024-03-26 16:37 ` dpdklab
2024-03-26 16:37 ` dpdklab
2024-03-26 16:37 ` dpdklab
2024-03-26 16:38 ` dpdklab
2024-03-26 16:38 ` dpdklab
2024-03-26 16:38 ` dpdklab
2024-03-26 16:38 ` dpdklab
2024-03-26 16:39 ` dpdklab
2024-03-26 16:39 ` dpdklab
2024-03-26 16:40 ` dpdklab
2024-03-26 16:40 ` dpdklab
2024-03-26 16:40 ` dpdklab
2024-03-26 16:41 ` dpdklab
2024-03-26 16:41 ` dpdklab
2024-03-26 16:41 ` dpdklab
2024-03-26 16:41 ` dpdklab
2024-03-26 16:42 ` dpdklab
2024-03-26 16:42 ` dpdklab
2024-03-26 16:42 ` dpdklab
2024-03-26 16:43 ` dpdklab
2024-03-26 16:43 ` dpdklab
2024-03-26 16:43 ` dpdklab
2024-03-26 16:43 ` dpdklab
2024-03-26 16:44 ` dpdklab
2024-03-26 16:44 ` dpdklab
2024-03-26 16:44 ` |SUCCESS| pw138811 [PATCH v2] " 0-day Robot
2024-03-26 16:44 ` |SUCCESS| pw138811 [PATCH] [v2] " dpdklab
2024-03-26 16:45 ` dpdklab
2024-03-26 16:45 ` dpdklab
2024-03-26 16:45 ` dpdklab
2024-03-26 16:45 ` dpdklab
2024-03-26 16:45 ` dpdklab
2024-03-26 16:46 ` dpdklab
2024-03-26 16:46 ` dpdklab
2024-03-26 16:46 ` dpdklab
2024-03-26 16:46 ` dpdklab
2024-03-26 16:47 ` dpdklab
2024-03-26 16:47 ` dpdklab
2024-03-26 16:47 ` dpdklab
2024-03-26 16:47 ` dpdklab
2024-03-26 16:48 ` dpdklab
2024-03-26 16:48 ` dpdklab
2024-03-26 16:48 ` dpdklab
2024-03-26 16:48 ` dpdklab
2024-03-26 16:48 ` dpdklab
2024-03-26 16:49 ` dpdklab
2024-03-26 16:49 ` dpdklab
2024-03-26 16:49 ` dpdklab
2024-03-26 16:49 ` dpdklab
2024-03-26 16:50 ` dpdklab
2024-03-26 16:50 ` dpdklab
2024-03-26 16:50 ` dpdklab
2024-03-26 16:50 ` dpdklab
2024-03-26 16:50 ` dpdklab
2024-03-26 16:55 ` dpdklab
2024-03-26 16:55 ` dpdklab
2024-03-26 17:07 ` dpdklab
2024-03-26 17:24 ` dpdklab
2024-03-26 17:53 ` dpdklab
2024-04-01 23:53 ` dpdklab
2024-04-01 23:57 ` dpdklab
2024-04-02 0:01 ` dpdklab
2024-04-02 0:04 ` dpdklab
2024-04-02 0:31 ` 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=202403261527.42QFR5kk2894926@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).