From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120545 [PATCH v2] net/nfp: using the correct PCI name to look for the firmware
Date: Fri, 9 Dec 2022 00:06:51 +0800 [thread overview]
Message-ID: <202212081606.2B8G6pMa194342@localhost.localdomain> (raw)
In-Reply-To: <20221208033116.34163-1-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120545
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thu, 8 Dec 2022 11:31:16 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6f59b7f0082ab8ffa79e87b1625279903b74ab05
120545 --> 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:[~2022-12-12 11:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221208033116.34163-1-chaoyong.he@corigine.com>
2022-12-08 3:31 ` checkpatch
2022-12-08 5:03 ` 0-day Robot
2022-12-08 16:06 ` qemudev [this message]
2022-12-08 16:07 ` qemudev
2022-12-08 16:42 ` qemudev
2022-12-08 16:43 ` qemudev
2022-12-10 0:31 ` qemudev
2022-12-10 0:32 ` qemudev
2022-12-08 7:10 |SUCCESS| pw120545 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-08 6:34 dpdklab
2022-12-08 6:34 dpdklab
2022-12-08 6:19 dpdklab
2022-12-08 6:18 dpdklab
2022-12-08 6:18 dpdklab
2022-12-08 6:17 dpdklab
2022-12-08 6:01 dpdklab
2022-12-08 5:54 dpdklab
2022-12-08 5:38 dpdklab
2022-12-08 5:32 dpdklab
2022-12-08 5:26 dpdklab
2022-12-08 4:33 dpdklab
2022-12-08 4:28 dpdklab
2022-12-08 4:21 dpdklab
2022-12-08 4:20 dpdklab
2022-12-08 4:14 dpdklab
2022-12-08 4:13 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=202212081606.2B8G6pMa194342@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).