From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121019-121026 [PATCH V1 11/11] net/mlx5/hws: add debug details for cross gvmi
Date: Mon, 19 Dec 2022 16:18:19 +0800 [thread overview]
Message-ID: <202212190818.2BJ8IJxD508052@localhost.localdomain> (raw)
In-Reply-To: <20221219082416.2223812-12-erezsh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121026
_Compilation OK_
Submitter: Erez Shitrit <erezsh@nvidia.com>
Date: Mon, 19 Dec 2022 10:24:06 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 6a738ebe90301c989219544c2894b422793e4861
121019-121026 --> 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:[~2022-12-19 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221219082416.2223812-12-erezsh@nvidia.com>
2022-12-19 8:18 ` qemudev [this message]
2022-12-19 8:22 ` qemudev
2022-12-19 8:26 ` |WARNING| pw121026 " checkpatch
2022-12-19 9:19 ` |SUCCESS| " 0-day Robot
2022-12-19 13:24 |SUCCESS| pw121019-121026 [PATCH] [V1, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-19 11:54 dpdklab
2022-12-19 11:54 dpdklab
2022-12-19 11:53 dpdklab
2022-12-19 11:46 dpdklab
2022-12-19 11:33 dpdklab
2022-12-19 11:33 dpdklab
2022-12-19 11:25 dpdklab
2022-12-19 11:25 dpdklab
2022-12-19 11:25 dpdklab
2022-12-19 10:55 dpdklab
2022-12-19 9:38 dpdklab
2022-12-19 9:12 dpdklab
2022-12-19 9:07 dpdklab
2022-12-19 8:56 dpdklab
2022-12-19 8:55 dpdklab
2022-12-19 8:51 dpdklab
2022-12-19 8:50 dpdklab
2022-12-19 8:49 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=202212190818.2BJ8IJxD508052@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).