From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138769 [PATCH v4] graph: expose node context as pointers
Date: Tue, 26 Mar 2024 00:10:21 +0800 [thread overview]
Message-ID: <202403251610.42PGALnL2551210@localhost.localdomain> (raw)
In-Reply-To: <20240325163108.816996-3-rjarry@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138769
_Compilation OK_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Mon, 25 Mar 2024 17:31:09 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73
138769 --> 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-25 16:35 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240325163108.816996-3-rjarry@redhat.com>
2024-03-25 16:10 ` qemudev [this message]
2024-03-25 16:14 ` qemudev
2024-03-25 16:33 ` checkpatch
2024-03-25 17:24 ` 0-day Robot
2024-03-25 18:50 ` |SUCCESS| pw138769 [PATCH] [v4] graph: expose node context as pointe dpdklab
2024-03-25 18:50 ` dpdklab
2024-03-25 18:51 ` dpdklab
2024-03-25 18:51 ` dpdklab
2024-03-25 18:51 ` dpdklab
2024-03-25 18:52 ` dpdklab
2024-03-25 18:52 ` dpdklab
2024-03-25 18:53 ` dpdklab
2024-03-25 18:53 ` dpdklab
2024-03-25 18:53 ` dpdklab
2024-03-25 18:53 ` dpdklab
2024-03-25 18:54 ` dpdklab
2024-03-25 18:54 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:58 ` dpdklab
2024-03-25 18:58 ` dpdklab
2024-03-25 18:58 ` dpdklab
2024-03-25 18:58 ` dpdklab
2024-03-25 18:59 ` dpdklab
2024-03-25 18:59 ` dpdklab
2024-03-25 18:59 ` dpdklab
2024-03-25 18:59 ` dpdklab
2024-03-25 19:00 ` dpdklab
2024-03-25 19:01 ` dpdklab
2024-03-25 19:01 ` dpdklab
2024-03-25 19:02 ` dpdklab
2024-03-25 19:02 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:06 ` dpdklab
2024-03-25 19:07 ` dpdklab
2024-03-25 19:08 ` dpdklab
2024-03-25 19:10 ` dpdklab
2024-03-25 19:10 ` dpdklab
2024-03-25 19:12 ` dpdklab
2024-03-25 19:13 ` dpdklab
2024-03-25 19:14 ` dpdklab
2024-03-25 19:14 ` dpdklab
2024-03-25 19:14 ` dpdklab
2024-03-25 19:16 ` dpdklab
2024-03-25 19:18 ` dpdklab
2024-03-25 19:19 ` dpdklab
2024-03-25 19:20 ` dpdklab
2024-03-25 19:20 ` dpdklab
2024-03-25 19:21 ` dpdklab
2024-03-25 19:24 ` dpdklab
2024-03-25 19:24 ` dpdklab
2024-03-25 19:25 ` dpdklab
2024-03-25 19:26 ` dpdklab
2024-03-25 19:32 ` dpdklab
2024-03-25 20:12 ` dpdklab
2024-03-25 20:22 ` dpdklab
2024-03-25 20:48 ` dpdklab
2024-03-25 21:36 ` dpdklab
2024-04-01 16:22 ` dpdklab
2024-04-01 16:26 ` dpdklab
2024-04-01 16:30 ` dpdklab
2024-04-01 16:34 ` dpdklab
2024-04-01 16:54 ` 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=202403251610.42PGALnL2551210@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).