From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125423 [PATCH v2] common/mlx5: fix the sysfs port name translation
Date: Thu, 23 Mar 2023 14:10:47 +0800 [thread overview]
Message-ID: <202303230610.32N6AlCW502636@localhost.localdomain> (raw)
In-Reply-To: <20230322113412.685653-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125423
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wed, 22 Mar 2023 13:34:12 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 33949800f1afcb7527b6e36c60c1548687ccb673
125423 --> 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:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230322113412.685653-1-bingz@nvidia.com>
2023-03-22 11:36 ` checkpatch
2023-03-22 13:59 ` 0-day Robot
2023-03-23 6:10 ` qemudev [this message]
2023-03-23 6:11 ` qemudev
2023-03-22 18:58 |SUCCESS| pw125423 [PATCH] [v2] " dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 18:59 dpdklab
2023-03-22 19:00 dpdklab
2023-03-22 19:03 dpdklab
2023-03-22 19:05 dpdklab
2023-03-22 19:08 dpdklab
2023-03-22 19:09 dpdklab
2023-03-22 19:13 dpdklab
2023-03-22 19:15 dpdklab
2023-03-22 19:18 dpdklab
2023-03-22 19:20 dpdklab
2023-03-22 19:21 dpdklab
2023-03-22 19:25 dpdklab
2023-03-22 19:30 dpdklab
2023-03-22 19:34 dpdklab
2023-03-22 19:54 dpdklab
2023-03-22 20:53 dpdklab
2023-03-22 22:59 dpdklab
2023-03-22 23:25 dpdklab
2023-03-23 21:29 dpdklab
2023-03-23 23:03 dpdklab
2023-03-24 4:37 dpdklab
2023-03-24 4:39 dpdklab
2023-03-24 21:42 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=202303230610.32N6AlCW502636@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).