From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123978-123999 [PATCH v7 22/22] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Thu, 16 Feb 2023 01:16:06 +0800 [thread overview]
Message-ID: <202302151716.31FHG6Dv896320@localhost.localdomain> (raw)
In-Reply-To: <20230215172341.1525320-23-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123999
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 15 Feb 2023 09:23:20 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6fdf32d1e318c00d26aa7ef09834dc2a1bda86c5
123978-123999 --> 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-15 17:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230215172341.1525320-23-stephen@networkplumber.org>
2023-02-15 17:16 ` qemudev [this message]
2023-02-15 17:20 ` qemudev
2023-02-15 17:27 ` |SUCCESS| pw123999 " checkpatch
2023-02-15 19:59 ` |FAILURE| " 0-day Robot
2023-02-15 18:00 |SUCCESS| pw123978-123999 [PATCH] [v7, " dpdklab
2023-02-15 18:01 dpdklab
2023-02-15 18:03 dpdklab
2023-02-15 18:10 dpdklab
2023-02-15 18:14 dpdklab
2023-02-15 18:15 dpdklab
2023-02-15 18:21 dpdklab
2023-02-15 18:30 dpdklab
2023-02-15 19:49 dpdklab
2023-02-15 19:59 dpdklab
2023-02-15 20:14 dpdklab
2023-02-15 20:18 dpdklab
2023-02-15 20:19 dpdklab
2023-02-15 20:21 dpdklab
2023-02-15 20:33 dpdklab
2023-02-15 20:36 dpdklab
2023-02-15 20:38 dpdklab
2023-02-15 20:43 dpdklab
2023-02-15 20:47 dpdklab
2023-02-15 21:00 dpdklab
2023-02-15 21:10 dpdklab
2023-02-15 21:10 dpdklab
2023-02-17 6:35 dpdklab
2023-02-18 23:15 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=202302151716.31FHG6Dv896320@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).