From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123828-123846 [PATCH v4 19/19] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Tue, 14 Feb 2023 03:56:46 +0800 [thread overview]
Message-ID: <202302131956.31DJukEn3730355@localhost.localdomain> (raw)
In-Reply-To: <20230213195551.1146298-20-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123846
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 13 Feb 2023 11:55:33 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 39d469a7eb4f157923be73aea0b0cc1015860ca7
123828-123846 --> 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-13 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230213195551.1146298-20-stephen@networkplumber.org>
2023-02-13 19:56 ` qemudev [this message]
2023-02-13 20:00 ` qemudev
2023-02-13 20:03 ` |SUCCESS| pw123846 " checkpatch
2023-02-14 0:59 ` |FAILURE| " 0-day Robot
2023-02-13 20:30 |SUCCESS| pw123828-123846 [PATCH] [v4, " dpdklab
2023-02-13 20:32 dpdklab
2023-02-13 20:33 dpdklab
2023-02-13 20:39 dpdklab
2023-02-13 20:41 dpdklab
2023-02-13 20:45 dpdklab
2023-02-13 20:48 dpdklab
2023-02-13 20:52 dpdklab
2023-02-14 6:50 dpdklab
2023-02-14 7:09 dpdklab
2023-02-14 7:24 dpdklab
2023-02-14 7:25 dpdklab
2023-02-14 7:26 dpdklab
2023-02-14 7:30 dpdklab
2023-02-14 7:31 dpdklab
2023-02-14 7:33 dpdklab
2023-02-14 7:34 dpdklab
2023-02-14 7:37 dpdklab
2023-02-14 7:40 dpdklab
2023-02-14 7:41 dpdklab
2023-02-14 7:41 dpdklab
2023-02-16 1:03 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=202302131956.31DJukEn3730355@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).