From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123909-123930 [PATCH v6 22/22] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Wed, 15 Feb 2023 06:40:33 +0800 [thread overview]
Message-ID: <202302142240.31EMeXjZ114548@localhost.localdomain> (raw)
In-Reply-To: <20230214224735.1404326-23-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123930
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 14 Feb 2023 14:47:14 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 04ed18cd41f12ea1487581731ef56185d902d827
123909-123930 --> 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-14 22:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230214224735.1404326-23-stephen@networkplumber.org>
2023-02-14 22:40 ` qemudev [this message]
2023-02-14 22:44 ` qemudev
2023-02-14 22:50 ` |SUCCESS| pw123930 " checkpatch
2023-02-15 1:19 ` |FAILURE| " 0-day Robot
2023-02-14 23:19 |SUCCESS| pw123909-123930 [PATCH] [v6, " dpdklab
2023-02-14 23:22 dpdklab
2023-02-14 23:25 dpdklab
2023-02-14 23:28 dpdklab
2023-02-14 23:34 dpdklab
2023-02-14 23:42 dpdklab
2023-02-14 23:43 dpdklab
2023-02-14 23:50 dpdklab
2023-02-15 0:25 dpdklab
2023-02-15 0:41 dpdklab
2023-02-15 0:43 dpdklab
2023-02-15 0:50 dpdklab
2023-02-15 0:51 dpdklab
2023-02-15 0:53 dpdklab
2023-02-15 0:55 dpdklab
2023-02-15 0:59 dpdklab
2023-02-15 1:02 dpdklab
2023-02-15 1:02 dpdklab
2023-02-15 1:24 dpdklab
2023-02-15 1:31 dpdklab
2023-02-15 1:33 dpdklab
2023-02-15 1:33 dpdklab
2023-02-16 14:04 dpdklab
2023-02-18 14:02 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=202302142240.31EMeXjZ114548@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).