From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124356-124355 [PATCH 2/2] app/testpmd: user assigned flow ID to flows
Date: Wed, 22 Feb 2023 22:01:16 +0800 [thread overview]
Message-ID: <202302221401.31ME1GvE1979281@localhost.localdomain> (raw)
In-Reply-To: <20230222141139.3233715-2-elibr@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124355
_Compilation OK_
Submitter: Eli Britstein <elibr@nvidia.com>
Date: Wed, 22 Feb 2023 16:11:37 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 418f86c426f23ad3ffd397e69d19e8d6b5577e67
124356-124355 --> 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-02-22 14:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230222141139.3233715-2-elibr@nvidia.com>
2023-02-22 14:01 ` qemudev [this message]
2023-02-22 14:05 ` qemudev
2023-02-22 14:12 ` |SUCCESS| pw124355 " checkpatch
2023-02-22 16:39 ` |FAILURE| " 0-day Robot
2023-02-22 14:39 |SUCCESS| pw124356-124355 [PATCH] [2/2] " dpdklab
2023-02-22 14:42 dpdklab
2023-02-22 14:43 dpdklab
2023-02-22 14:43 dpdklab
2023-02-22 14:49 dpdklab
2023-02-22 14:54 dpdklab
2023-02-22 14:55 dpdklab
2023-02-22 14:59 dpdklab
2023-02-22 15:02 dpdklab
2023-02-22 16:57 dpdklab
2023-02-22 17:05 dpdklab
2023-02-22 17:11 dpdklab
2023-02-22 17:12 dpdklab
2023-02-22 17:14 dpdklab
2023-02-22 17:19 dpdklab
2023-02-22 17:21 dpdklab
2023-02-22 17:23 dpdklab
2023-02-22 17:23 dpdklab
2023-02-22 17:32 dpdklab
2023-02-22 17:33 dpdklab
2023-02-22 17:42 dpdklab
2023-02-22 17:42 dpdklab
2023-02-22 21:04 dpdklab
2023-02-24 7:07 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=202302221401.31ME1GvE1979281@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).