From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124410-124431 [PATCH v11 22/22] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Thu, 23 Feb 2023 05:46:59 +0800 [thread overview]
Message-ID: <202302222146.31MLkx572381561@localhost.localdomain> (raw)
In-Reply-To: <20230222215541.158205-23-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124431
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 22 Feb 2023 13:55:20 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124410-124431 --> 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-22 22:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230222215541.158205-23-stephen@networkplumber.org>
2023-02-22 21:46 ` qemudev [this message]
2023-02-22 21:50 ` qemudev
2023-02-22 21:59 ` |SUCCESS| pw124431 " checkpatch
2023-02-23 0:39 ` 0-day Robot
2023-02-24 15:00 |SUCCESS| pw124410-124431 [PATCH] [v11, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 6:37 dpdklab
2023-02-23 2:22 dpdklab
2023-02-23 2:21 dpdklab
2023-02-23 2:19 dpdklab
2023-02-23 2:16 dpdklab
2023-02-23 2:15 dpdklab
2023-02-23 2:10 dpdklab
2023-02-23 2:08 dpdklab
2023-02-23 2:06 dpdklab
2023-02-23 2:05 dpdklab
2023-02-23 2:03 dpdklab
2023-02-23 2:00 dpdklab
2023-02-23 1:56 dpdklab
2023-02-23 1:46 dpdklab
2023-02-22 23:09 dpdklab
2023-02-22 22:56 dpdklab
2023-02-22 22:50 dpdklab
2023-02-22 22:49 dpdklab
2023-02-22 22:47 dpdklab
2023-02-22 22:44 dpdklab
2023-02-22 22:35 dpdklab
2023-02-22 22:32 dpdklab
2023-02-22 22:32 dpdklab
2023-02-22 22:28 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=202302222146.31MLkx572381561@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).