From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124191-124198 [PATCH v2 9/9] app/testpmd: factorize fwd engine Tx
Date: Tue, 21 Feb 2023 00:31:20 +0800 [thread overview]
Message-ID: <202302201631.31KGVKWG3701641@localhost.localdomain> (raw)
In-Reply-To: <20230220164103.3041538-10-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124198
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 20 Feb 2023 17:40:55 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6ff028f0add995c08d650bd5450b7c39c38a8a2b
124191-124198 --> 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-20 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230220164103.3041538-10-david.marchand@redhat.com>
2023-02-20 16:31 ` qemudev [this message]
2023-02-20 16:35 ` qemudev
2023-02-20 16:43 ` |SUCCESS| pw124198 " checkpatch
2023-02-20 18:59 ` |FAILURE| " 0-day Robot
2023-02-20 17:33 |SUCCESS| pw124191-124198 [PATCH] [v2, " dpdklab
2023-02-20 17:38 dpdklab
2023-02-20 17:38 dpdklab
2023-02-20 17:42 dpdklab
2023-02-20 18:10 dpdklab
2023-02-20 19:38 dpdklab
2023-02-20 20:00 dpdklab
2023-02-20 20:10 dpdklab
2023-02-20 20:14 dpdklab
2023-02-20 20:14 dpdklab
2023-02-20 20:20 dpdklab
2023-02-20 20:21 dpdklab
2023-02-20 20:28 dpdklab
2023-02-20 20:29 dpdklab
2023-02-20 20:31 dpdklab
2023-02-20 20:31 dpdklab
2023-02-20 20:34 dpdklab
2023-02-20 20:46 dpdklab
2023-02-20 20:46 dpdklab
2023-02-20 23:00 dpdklab
2023-02-21 18:21 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=202302201631.31KGVKWG3701641@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).