From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124224-124245 [PATCH v8 22/22] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Tue, 21 Feb 2023 07:28:23 +0800 [thread overview]
Message-ID: <202302202328.31KNSN2p4143061@localhost.localdomain> (raw)
In-Reply-To: <20230220233556.168553-23-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124245
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 20 Feb 2023 15:35:35 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9bd5ebca59c865aead7096358fb733e53a72007b
124224-124245 --> 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-20 23:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230220233556.168553-23-stephen@networkplumber.org>
2023-02-20 23:28 ` qemudev [this message]
2023-02-20 23:32 ` qemudev
2023-02-20 23:38 ` |SUCCESS| pw124245 " checkpatch
2023-02-21 2:19 ` |FAILURE| " 0-day Robot
2023-02-22 9:02 |SUCCESS| pw124224-124245 [PATCH] [v8, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 7:19 dpdklab
2023-02-21 4:43 dpdklab
2023-02-21 4:43 dpdklab
2023-02-21 4:42 dpdklab
2023-02-21 4:41 dpdklab
2023-02-21 4:40 dpdklab
2023-02-21 4:38 dpdklab
2023-02-21 4:34 dpdklab
2023-02-21 4:32 dpdklab
2023-02-21 4:30 dpdklab
2023-02-21 4:30 dpdklab
2023-02-21 4:28 dpdklab
2023-02-21 4:27 dpdklab
2023-02-21 4:04 dpdklab
2023-02-21 0:32 dpdklab
2023-02-21 0:27 dpdklab
2023-02-21 0:24 dpdklab
2023-02-21 0:23 dpdklab
2023-02-21 0:20 dpdklab
2023-02-21 0:19 dpdklab
2023-02-21 0:18 dpdklab
2023-02-21 0:12 dpdklab
2023-02-21 0:11 dpdklab
2023-02-21 0:08 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=202302202328.31KNSN2p4143061@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).