From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126560 [PATCH] net/mana: return probe failure if there is no device found
Date: Thu, 27 Apr 2023 10:07:27 +0800 [thread overview]
Message-ID: <202304270207.33R27R9i2522366@localhost.localdomain> (raw)
In-Reply-To: <1682561915-7204-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126560
_Compilation OK_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Wed, 26 Apr 2023 19:18:35 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b6367469a9368234bc5ed931dc9ba29474e7d347
126560 --> 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-04-27 2:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1682561915-7204-1-git-send-email-longli@linuxonhyperv.com>
2023-04-27 2:07 ` qemudev [this message]
2023-04-27 2:11 ` qemudev
2023-04-27 2:20 ` |WARNING| " checkpatch
2023-04-27 3:39 ` |SUCCESS| " 0-day Robot
2023-04-27 3:42 dpdklab
2023-04-27 3:45 dpdklab
2023-04-27 3:45 dpdklab
2023-04-27 3:56 dpdklab
2023-04-27 4:08 dpdklab
2023-04-27 4:22 dpdklab
2023-04-27 4:58 dpdklab
2023-04-27 4:58 dpdklab
2023-04-27 4:58 dpdklab
2023-04-27 5:02 dpdklab
2023-04-27 5:09 dpdklab
2023-04-27 5:17 dpdklab
2023-04-27 5:20 dpdklab
2023-04-27 5:23 dpdklab
2023-04-27 5:28 dpdklab
2023-04-27 5:28 dpdklab
2023-04-27 5:30 dpdklab
2023-04-27 7:55 dpdklab
2023-04-27 20:41 dpdklab
2023-04-27 23:04 dpdklab
2023-04-28 15:43 dpdklab
2023-04-28 18:12 dpdklab
2023-04-28 20:32 dpdklab
2023-04-28 20:38 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=202304270207.33R27R9i2522366@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).