From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124156-124164 [PATCH v4 9/9] table: enable build on Windows
Date: Mon, 20 Feb 2023 07:05:18 +0800 [thread overview]
Message-ID: <202302192305.31JN5Ixo3039393@localhost.localdomain> (raw)
In-Reply-To: <20230219231416.22524-10-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124164
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sun, 19 Feb 2023 15:14:08 -0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: a5d34ecbb4b017e1b6c20a1f28127ffeaa1237af
124156-124164 --> 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-19 23:19 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230219231416.22524-10-stephen@networkplumber.org>
2023-02-19 23:05 ` qemudev [this message]
2023-02-19 23:09 ` qemudev
2023-02-19 23:16 ` |SUCCESS| pw124164 " checkpatch
2023-02-20 0:59 ` 0-day Robot
2023-02-19 23:39 |SUCCESS| pw124156-124164 [PATCH] [v4, " dpdklab
2023-02-19 23:43 dpdklab
2023-02-19 23:45 dpdklab
2023-02-19 23:49 dpdklab
2023-02-19 23:50 dpdklab
2023-02-19 23:54 dpdklab
2023-02-19 23:57 dpdklab
2023-02-20 0:05 dpdklab
2023-02-20 0:17 dpdklab
2023-02-20 0:45 dpdklab
2023-02-20 0:49 dpdklab
2023-02-20 0:50 dpdklab
2023-02-20 0:54 dpdklab
2023-02-20 0:55 dpdklab
2023-02-20 1:04 dpdklab
2023-02-20 1:10 dpdklab
2023-02-20 1:14 dpdklab
2023-02-20 1:15 dpdklab
2023-02-20 1:18 dpdklab
2023-02-20 1:19 dpdklab
2023-02-20 1:20 dpdklab
2023-02-20 1:21 dpdklab
2023-02-20 1:21 dpdklab
2023-02-20 1:42 dpdklab
2023-02-20 17:51 dpdklab
2023-03-09 20:58 dpdklab
2023-03-09 21:02 dpdklab
2023-03-09 21:06 dpdklab
2023-03-09 21:08 dpdklab
2023-03-09 21:10 dpdklab
2023-03-09 21:13 dpdklab
2023-03-09 21:14 dpdklab
2023-03-09 21:15 dpdklab
2023-03-09 21:16 dpdklab
2023-03-09 21:18 dpdklab
2023-03-09 21:19 dpdklab
2023-03-09 21:20 dpdklab
2023-03-09 21:26 dpdklab
2023-03-10 1:25 dpdklab
2023-03-10 3:40 dpdklab
2023-03-10 5:39 dpdklab
2023-03-10 8:56 dpdklab
2023-03-10 9:01 dpdklab
2023-03-10 9:04 dpdklab
2023-03-10 9:10 dpdklab
2023-03-10 9:15 dpdklab
2023-03-10 9:23 dpdklab
2023-03-10 9:24 dpdklab
2023-03-10 9:37 dpdklab
2023-03-10 9:39 dpdklab
2023-03-10 9:40 dpdklab
2023-03-10 9:45 dpdklab
2023-03-10 10:07 dpdklab
2023-03-10 10:14 dpdklab
2023-03-10 10:22 dpdklab
2023-03-10 10:23 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=202302192305.31JN5Ixo3039393@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).