From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129341 [PATCH] net/mlx5: fix query for NIC flow cap
Date: Thu, 6 Jul 2023 20:24:12 +0800 [thread overview]
Message-ID: <202307061224.366COCRf3421597@localhost.localdomain> (raw)
In-Reply-To: <20230706123616.2484-1-orika@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129341
_Compilation OK_
Submitter: Ori Kam <orika@nvidia.com>
Date: Thu, 6 Jul 2023 15:36:15 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 93906ee021f568766dd01c24ec32a57af7b123b1
129341 --> 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-07-06 12:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230706123616.2484-1-orika@nvidia.com>
2023-07-06 12:24 ` qemudev [this message]
2023-07-06 12:28 ` qemudev
2023-07-06 12:37 ` |WARNING| " checkpatch
2023-07-06 13:59 ` |SUCCESS| " 0-day Robot
2023-07-06 13:18 dpdklab
2023-07-06 13:18 dpdklab
2023-07-06 13:18 dpdklab
2023-07-06 13:19 dpdklab
2023-07-06 13:19 dpdklab
2023-07-06 13:19 dpdklab
2023-07-06 13:19 dpdklab
2023-07-06 13:21 dpdklab
2023-07-06 13:24 dpdklab
2023-07-06 13:29 dpdklab
2023-07-06 13:29 dpdklab
2023-07-06 13:31 dpdklab
2023-07-06 19:58 dpdklab
2023-07-06 21:32 dpdklab
2023-07-06 21:53 dpdklab
2023-07-07 5:08 dpdklab
2023-07-08 20:06 dpdklab
2023-07-08 20:25 dpdklab
2023-07-11 18:37 dpdklab
2023-07-12 19:13 dpdklab
2023-07-12 19:22 dpdklab
2023-07-12 20:50 dpdklab
2023-07-12 20:55 dpdklab
2023-07-13 10:43 dpdklab
2023-07-13 10:48 dpdklab
2023-07-13 10:53 dpdklab
2023-07-13 21:15 dpdklab
2023-07-14 0:34 dpdklab
2023-07-14 0:34 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=202307061224.366COCRf3421597@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).