From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126250 [PATCH] ethdev: add flow rule actions update API
Date: Wed, 19 Apr 2023 03:47:12 +0800 [thread overview]
Message-ID: <202304181947.33IJlCxc473249@localhost.localdomain> (raw)
In-Reply-To: <20230418195807.352514-1-akozyrev@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126250
_Compilation OK_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Tue, 18 Apr 2023 22:58:07 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f649fd010f2dd3a97e15f2ef106440a79f6c95fb
126250 --> 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-04-18 20:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230418195807.352514-1-akozyrev@nvidia.com>
2023-04-18 19:47 ` qemudev [this message]
2023-04-18 19:51 ` qemudev
2023-04-18 19:59 ` |WARNING| " checkpatch
2023-04-18 20:59 ` |SUCCESS| " 0-day Robot
2023-04-18 23:11 dpdklab
2023-04-18 23:12 dpdklab
2023-04-18 23:17 dpdklab
2023-04-18 23:19 dpdklab
2023-04-18 23:20 dpdklab
2023-04-18 23:21 dpdklab
2023-04-18 23:21 dpdklab
2023-04-18 23:23 dpdklab
2023-04-18 23:24 dpdklab
2023-04-18 23:24 dpdklab
2023-04-18 23:28 dpdklab
2023-04-18 23:33 dpdklab
2023-04-18 23:36 dpdklab
2023-04-19 0:31 dpdklab
2023-04-19 0:54 dpdklab
2023-04-19 0:58 dpdklab
2023-04-19 1:02 dpdklab
2023-04-19 1:03 dpdklab
2023-04-19 1:05 dpdklab
2023-04-19 1:10 dpdklab
2023-04-19 1:17 dpdklab
2023-04-19 1:20 dpdklab
2023-04-19 1:22 dpdklab
2023-04-19 1:23 dpdklab
2023-04-19 1:27 dpdklab
2023-04-19 9:37 dpdklab
2023-04-19 10:18 dpdklab
2023-04-19 14:09 dpdklab
2023-04-19 14:09 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=202304181947.33IJlCxc473249@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).