From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124335 [PATCH] net/mana: use RTE_LOG_DP for logs on datapath
Date: Wed, 22 Feb 2023 04:32:11 +0800 [thread overview]
Message-ID: <202302212032.31LKWBV71472792@localhost.localdomain> (raw)
In-Reply-To: <1677012145-3559-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124335
_Compilation OK_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tue, 21 Feb 2023 12:42:25 -0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 14a61443b2f99f4d14f242c1f8636bfacbaaf32c
124335 --> 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-21 20:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1677012145-3559-1-git-send-email-longli@linuxonhyperv.com>
2023-02-21 20:32 ` qemudev [this message]
2023-02-21 20:36 ` qemudev
2023-02-21 20:43 ` |WARNING| " checkpatch
2023-02-21 23:39 ` |SUCCESS| " 0-day Robot
2023-02-23 22:39 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 8:41 dpdklab
2023-02-22 7:09 dpdklab
2023-02-22 7:09 dpdklab
2023-02-22 7:08 dpdklab
2023-02-22 7:06 dpdklab
2023-02-22 7:06 dpdklab
2023-02-22 7:05 dpdklab
2023-02-22 7:03 dpdklab
2023-02-22 7:03 dpdklab
2023-02-22 7:00 dpdklab
2023-02-22 6:52 dpdklab
2023-02-22 6:46 dpdklab
2023-02-22 6:46 dpdklab
2023-02-22 6:40 dpdklab
2023-02-22 6:26 dpdklab
2023-02-21 23:29 dpdklab
2023-02-21 23:09 dpdklab
2023-02-21 22:15 dpdklab
2023-02-21 22:08 dpdklab
2023-02-21 21:46 dpdklab
2023-02-21 21:33 dpdklab
2023-02-21 21:25 dpdklab
2023-02-21 21:18 dpdklab
2023-02-21 21:14 dpdklab
2023-02-21 21:10 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=202302212032.31LKWBV71472792@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).