From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126952 [PATCH] net/mlx5: fix drop action attribute validation
Date: Thu, 18 May 2023 04:25:30 +0800 [thread overview]
Message-ID: <202305172025.34HKPUjC2097520@localhost.localdomain> (raw)
In-Reply-To: <20230517203614.538262-1-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126952
_Compilation OK_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wed, 17 May 2023 20:36:14 +0000
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126952 --> 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-05-17 20:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230517203614.538262-1-dsosnowski@nvidia.com>
2023-05-17 20:25 ` qemudev [this message]
2023-05-17 20:29 ` qemudev
2023-05-17 20:38 ` checkpatch
2023-05-17 21:59 ` 0-day Robot
2023-05-17 22:58 dpdklab
2023-05-17 23:02 dpdklab
2023-05-17 23:03 dpdklab
2023-05-17 23:05 dpdklab
2023-05-17 23:07 dpdklab
2023-05-17 23:20 dpdklab
2023-05-17 23:20 dpdklab
2023-05-17 23:32 dpdklab
2023-05-17 23:36 dpdklab
2023-05-17 23:40 dpdklab
2023-05-17 23:41 dpdklab
2023-05-17 23:44 dpdklab
2023-05-17 23:46 dpdklab
2023-05-17 23:53 dpdklab
2023-05-17 23:56 dpdklab
2023-05-17 23:57 dpdklab
2023-05-17 23:59 dpdklab
2023-05-18 0:01 dpdklab
2023-05-18 0:01 dpdklab
2023-05-18 0:02 dpdklab
2023-05-18 0:07 dpdklab
2023-05-18 0:08 dpdklab
2023-05-18 0:11 dpdklab
2023-05-18 0:14 dpdklab
2023-05-18 0:20 dpdklab
2023-05-18 0:20 dpdklab
2023-05-18 0:28 dpdklab
2023-05-18 0:35 dpdklab
2023-05-18 5:18 dpdklab
2023-05-18 5:19 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=202305172025.34HKPUjC2097520@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).