From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122349 [PATCH] graph: fix node shrink
Date: Thu, 19 Jan 2023 18:25:21 +0800 [thread overview]
Message-ID: <202301191025.30JAPLv62758133@localhost.localdomain> (raw)
In-Reply-To: <20230119103234.841173-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122349
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu, 19 Jan 2023 11:32:34 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5b45dfaab907fb14527a6328353bee290fa7c298
122349 --> 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-01-19 10:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230119103234.841173-1-david.marchand@redhat.com>
2023-01-19 10:25 ` qemudev [this message]
2023-01-19 10:29 ` qemudev
2023-01-19 10:33 ` checkpatch
2023-01-19 11:39 ` 0-day Robot
2023-01-20 9:03 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-20 1:19 dpdklab
2023-01-19 21:07 dpdklab
2023-01-19 21:06 dpdklab
2023-01-19 21:06 dpdklab
2023-01-19 21:06 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:05 dpdklab
2023-01-19 21:04 dpdklab
2023-01-19 15:01 dpdklab
2023-01-19 13:38 dpdklab
2023-01-19 11:21 dpdklab
2023-01-19 11:17 dpdklab
2023-01-19 11:09 dpdklab
2023-01-19 11:07 dpdklab
2023-01-19 11:06 dpdklab
2023-01-19 11:05 dpdklab
2023-01-19 11:01 dpdklab
2023-01-19 11: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=202301191025.30JAPLv62758133@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).