From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153839 [PATCH] ethdev: fix null error struct in flow configure
Date: Thu, 29 May 2025 13:23:16 +0800 [thread overview]
Message-ID: <202505290523.54T5NGaG3292069@localhost.localdomain> (raw)
In-Reply-To: <20250529055612.115265-1-mkashani@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/153839
_Compilation OK_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thu, 29 May 2025 08:56:10 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 466db466e2938c0d4e7f3dd75435483133f98770
153839 --> 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:[~2025-05-29 5:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529055612.115265-1-mkashani@nvidia.com>
2025-05-29 5:23 ` qemudev [this message]
2025-05-29 5:27 ` qemudev
2025-05-29 5:56 ` checkpatch
2025-05-29 7:04 ` 0-day Robot
2025-05-29 14:18 ` |PENDING| pw153839 [PATCH] ethdev: fix null error struct in flow con dpdklab
2025-05-29 14:23 ` |SUCCESS| " dpdklab
2025-05-29 14:36 ` dpdklab
2025-05-29 14:46 ` dpdklab
2025-05-29 15:31 ` |PENDING| " dpdklab
2025-05-29 16:08 ` dpdklab
2025-05-29 16:18 ` |SUCCESS| " dpdklab
2025-05-29 16:53 ` |PENDING| " dpdklab
2025-05-29 16:55 ` dpdklab
2025-05-29 16:58 ` |SUCCESS| " dpdklab
2025-05-29 17:01 ` dpdklab
2025-05-29 17:01 ` dpdklab
2025-05-29 17:01 ` dpdklab
2025-05-29 17:02 ` dpdklab
2025-05-29 17:03 ` dpdklab
2025-05-29 17:03 ` dpdklab
2025-05-29 17:25 ` |PENDING| " dpdklab
2025-05-29 17:29 ` dpdklab
2025-05-29 17:30 ` |SUCCESS| " dpdklab
2025-05-29 17:53 ` |WARNING| " dpdklab
2025-05-29 17:55 ` dpdklab
2025-05-29 18:02 ` |SUCCESS| " dpdklab
2025-05-29 18:38 ` |WARNING| " dpdklab
2025-05-29 21:16 ` |SUCCESS| " dpdklab
2025-05-29 22:25 ` dpdklab
2025-05-29 22:43 ` |PENDING| " dpdklab
2025-05-29 22:56 ` |WARNING| " dpdklab
2025-05-29 22:57 ` dpdklab
2025-05-29 23:13 ` dpdklab
2025-05-30 1:46 ` dpdklab
2025-05-30 2:02 ` |SUCCESS| " dpdklab
2025-05-30 2:13 ` dpdklab
2025-05-30 2:14 ` dpdklab
2025-05-30 2:16 ` dpdklab
2025-05-30 3:13 ` |WARNING| " dpdklab
2025-05-30 19:04 ` |SUCCESS| " dpdklab
2025-05-30 20:33 ` |WARNING| " dpdklab
2025-05-30 20:34 ` dpdklab
2025-05-30 20:36 ` dpdklab
2025-05-30 20:38 ` dpdklab
2025-05-30 22:43 ` |SUCCESS| " dpdklab
2025-05-30 22:54 ` dpdklab
2025-05-30 23:31 ` dpdklab
2025-05-30 23:39 ` dpdklab
2025-06-04 11:39 ` 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=202505290523.54T5NGaG3292069@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).