From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136223 [PATCH] ethdev: fast path async flow API
Date: Wed, 31 Jan 2024 01:56:30 +0800 [thread overview]
Message-ID: <202401301756.40UHuUsx842798@localhost.localdomain> (raw)
In-Reply-To: <20240130181751.1425388-1-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136223
_Compilation OK_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tue, 30 Jan 2024 20:17:50 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136223 --> 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:[~2024-01-30 18:21 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240130181751.1425388-1-dsosnowski@nvidia.com>
2024-01-30 17:56 ` qemudev [this message]
2024-01-30 18:00 ` qemudev
2024-01-30 18:19 ` checkpatch
2024-01-30 19:23 ` 0-day Robot
2024-01-30 21:47 dpdklab
2024-01-30 21:47 dpdklab
2024-01-30 21:47 dpdklab
2024-01-30 21:48 dpdklab
2024-01-30 21:49 dpdklab
2024-01-30 21:50 dpdklab
2024-01-30 21:51 dpdklab
2024-01-30 21:52 dpdklab
2024-01-30 21:52 dpdklab
2024-01-30 21:52 dpdklab
2024-01-30 21:53 dpdklab
2024-01-30 21:54 dpdklab
2024-01-30 21:55 dpdklab
2024-01-30 21:55 dpdklab
2024-01-30 21:56 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:58 dpdklab
2024-01-30 21:59 dpdklab
2024-01-30 21:59 dpdklab
2024-01-30 22:01 dpdklab
2024-01-30 22:01 dpdklab
2024-01-30 22:02 dpdklab
2024-01-30 22:03 dpdklab
2024-01-30 22:04 dpdklab
2024-01-30 22:04 dpdklab
2024-01-30 22:05 dpdklab
2024-01-30 22:09 dpdklab
2024-01-30 22:11 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:12 dpdklab
2024-01-30 22:13 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:14 dpdklab
2024-01-30 22:20 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:27 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:28 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:29 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:30 dpdklab
2024-01-30 22:31 dpdklab
2024-01-30 22:31 dpdklab
2024-01-30 22:33 dpdklab
2024-01-30 22:33 dpdklab
2024-01-30 22:34 dpdklab
2024-01-30 22:34 dpdklab
2024-01-30 22:35 dpdklab
2024-01-30 22:36 dpdklab
2024-01-30 22:37 dpdklab
2024-01-30 22:47 dpdklab
2024-01-30 22:51 dpdklab
2024-01-30 23:01 dpdklab
2024-01-30 23:12 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=202401301756.40UHuUsx842798@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).