From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121207-121219 [PATCH V1 11/11] net/mlx5/hws: add debug details for cross gvmi
Date: Wed, 21 Dec 2022 21:12:53 +0800 [thread overview]
Message-ID: <202212211312.2BLDCrPb2220002@localhost.localdomain> (raw)
In-Reply-To: <20221218150853.2167280-12-erezsh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121219
_Compilation OK_
Submitter: Erez Shitrit <erezsh@nvidia.com>
Date: Sun, 18 Dec 2022 17:08:42 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: ea40920417296397f14236e46604d10a8c571706
121207-121219 --> 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-21 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221218150853.2167280-12-erezsh@nvidia.com>
2022-12-21 10:20 ` |WARNING| pw121219 " checkpatch
2022-12-21 13:12 ` qemudev [this message]
2022-12-21 13:16 ` |SUCCESS| pw121207-121219 " qemudev
2022-12-22 3:13 |SUCCESS| pw121207-121219 [PATCH] [V1, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-22 1:35 dpdklab
2022-12-22 1:17 dpdklab
2022-12-22 1:17 dpdklab
2022-12-22 0:56 dpdklab
2022-12-22 0:28 dpdklab
2022-12-22 0:26 dpdklab
2022-12-22 0:09 dpdklab
2022-12-22 0:09 dpdklab
2022-12-22 0:03 dpdklab
2022-12-22 0:03 dpdklab
2022-12-21 15:06 dpdklab
2022-12-21 14:10 dpdklab
2022-12-21 14:03 dpdklab
2022-12-21 13:37 dpdklab
2022-12-21 13:30 dpdklab
2022-12-21 12:21 dpdklab
2022-12-21 12:08 dpdklab
2022-12-21 11:50 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=202212211312.2BLDCrPb2220002@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).