From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123626-123641 [PATCH v3 16/16] pipeline: replace RTE_LOGTYPE_PIPELINE with dynamic log type
Date: Fri, 10 Feb 2023 09:00:21 +0800 [thread overview]
Message-ID: <202302100100.31A10L98932272@localhost.localdomain> (raw)
In-Reply-To: <20230210010724.890413-17-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123641
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 9 Feb 2023 17:07:09 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 183bdfe224760b72d3cd44f5367c80b5ee073327
123626-123641 --> 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-02-10 1:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210010724.890413-17-stephen@networkplumber.org>
2023-02-10 1:00 ` qemudev [this message]
2023-02-10 1:04 ` qemudev
2023-02-10 1:10 ` |SUCCESS| pw123641 " checkpatch
2023-02-10 2:19 ` |FAILURE| " 0-day Robot
2023-02-10 1:41 |SUCCESS| pw123626-123641 [PATCH] [v3, " dpdklab
2023-02-10 1:47 dpdklab
2023-02-10 1:49 dpdklab
2023-02-10 1:53 dpdklab
2023-02-10 1:54 dpdklab
2023-02-10 2:01 dpdklab
2023-02-10 4:16 dpdklab
2023-02-11 12:43 dpdklab
2023-02-11 12:45 dpdklab
2023-02-11 12:55 dpdklab
2023-02-11 13:00 dpdklab
2023-02-11 13:08 dpdklab
2023-02-11 13:10 dpdklab
2023-02-11 13:12 dpdklab
2023-02-11 13:12 dpdklab
2023-02-11 13:13 dpdklab
2023-02-11 13:18 dpdklab
2023-02-11 13:19 dpdklab
2023-02-11 13:20 dpdklab
2023-02-11 13:21 dpdklab
2023-02-12 21:38 dpdklab
2023-02-12 22:56 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=202302100100.31A10L98932272@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).