From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125412 [PATCH V1] doc: add tested Intel platforms with Intel NICs
Date: Thu, 23 Mar 2023 14:19:05 +0800 [thread overview]
Message-ID: <202303230619.32N6J5rn503394@localhost.localdomain> (raw)
In-Reply-To: <20230322055130.43556-1-linglix.chen@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125412
_Compilation OK_
Submitter: Lingli Chen <linglix.chen@intel.com>
Date: Wed, 22 Mar 2023 01:51:30 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 1a80f6062cf74e4b689b8b9a4f905a24efec527a
125412 --> 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 prev parent reply other threads:[~2023-03-23 6:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230322055130.43556-1-linglix.chen@intel.com>
2023-03-22 7:00 ` checkpatch
2023-03-22 9:39 ` 0-day Robot
2023-03-23 6:19 ` qemudev [this message]
2023-03-23 6:19 ` qemudev
2023-03-22 7:55 |SUCCESS| pw125412 [PATCH] [V1] " dpdklab
2023-03-22 7:57 dpdklab
2023-03-22 7:59 dpdklab
2023-03-22 7:59 dpdklab
2023-03-22 8:00 dpdklab
2023-03-22 8:02 dpdklab
2023-03-22 8:02 dpdklab
2023-03-22 8:06 dpdklab
2023-03-22 8:07 dpdklab
2023-03-22 8:07 dpdklab
2023-03-22 8:08 dpdklab
2023-03-22 8:11 dpdklab
2023-03-22 8:15 dpdklab
2023-03-22 8:15 dpdklab
2023-03-22 8:20 dpdklab
2023-03-22 8:20 dpdklab
2023-03-22 8:28 dpdklab
2023-03-22 8:28 dpdklab
2023-03-22 8:30 dpdklab
2023-03-22 8:35 dpdklab
2023-03-22 8:45 dpdklab
2023-03-22 8:53 dpdklab
2023-03-22 9:23 dpdklab
2023-03-22 21:30 dpdklab
2023-03-22 21:35 dpdklab
2023-03-23 10:41 dpdklab
2023-03-23 12:44 dpdklab
2023-03-23 15:25 dpdklab
2023-03-23 18:00 dpdklab
2023-03-24 12:23 dpdklab
2023-03-24 13:07 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=202303230619.32N6J5rn503394@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).