From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127050 [PATCH v2] ethdev: add flow rule actions update API
Date: Fri, 19 May 2023 03:39:37 +0800 [thread overview]
Message-ID: <202305181939.34IJdbPZ3491053@localhost.localdomain> (raw)
In-Reply-To: <20230518194943.2338558-1-akozyrev@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127050
_Compilation OK_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thu, 18 May 2023 22:49:43 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a399d7b5a994e335c446d4b15d7622d71dd8848c
127050 --> 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-18 19:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230518194943.2338558-1-akozyrev@nvidia.com>
2023-05-18 19:39 ` qemudev [this message]
2023-05-18 19:43 ` qemudev
2023-05-18 19:51 ` checkpatch
2023-05-18 21:18 |SUCCESS| pw127050 [PATCH] [v2] " dpdklab
2023-05-18 21:18 dpdklab
2023-05-18 21:21 dpdklab
2023-05-18 21:22 dpdklab
2023-05-18 21:22 dpdklab
2023-05-18 21:24 dpdklab
2023-05-18 21:30 dpdklab
2023-05-18 21:41 dpdklab
2023-05-18 23:02 dpdklab
2023-05-18 23:02 dpdklab
2023-05-18 23:03 dpdklab
2023-05-18 23:04 dpdklab
2023-05-18 23:04 dpdklab
2023-05-18 23:15 dpdklab
2023-05-18 23:15 dpdklab
2023-05-18 23:17 dpdklab
2023-05-18 23:19 dpdklab
2023-05-18 23:19 dpdklab
2023-05-18 23:23 dpdklab
2023-05-19 0:01 dpdklab
2023-05-19 0:46 dpdklab
2023-05-19 0:52 dpdklab
2023-05-19 1:00 dpdklab
2023-05-19 1:15 dpdklab
2023-05-19 1:20 dpdklab
2023-05-19 13:17 dpdklab
2023-05-19 13:45 dpdklab
2023-05-19 18:37 dpdklab
2023-05-19 18:38 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=202305181939.34IJdbPZ3491053@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).