From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124283 [PATCH v2] app/testpmd: fix secondary process not forwarding
Date: Tue, 21 Feb 2023 16:00:33 +0800 [thread overview]
Message-ID: <202302210800.31L80XLB649454@localhost.localdomain> (raw)
In-Reply-To: <20230221154418.153972-1-shiyangx.he@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124283
_Compilation OK_
Submitter: Shiyang He <shiyangx.he@intel.com>
Date: Tue, 21 Feb 2023 15:44:18 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 74ef0e382c258b031e752c9ef5c6872a4da1c28d
124283 --> 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-21 8:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221154418.153972-1-shiyangx.he@intel.com>
2023-02-21 8:00 ` qemudev [this message]
2023-02-21 8:04 ` qemudev
2023-02-21 8:13 ` |WARNING| " checkpatch
2023-02-21 10:19 ` |SUCCESS| " 0-day Robot
2023-02-21 8:56 |SUCCESS| pw124283 [PATCH] [v2] " dpdklab
2023-02-21 8:57 dpdklab
2023-02-21 9:01 dpdklab
2023-02-21 9:05 dpdklab
2023-02-21 9:12 dpdklab
2023-02-21 9:16 dpdklab
2023-02-21 9:17 dpdklab
2023-02-21 9:24 dpdklab
2023-02-21 9:30 dpdklab
2023-02-21 9:37 dpdklab
2023-02-21 13:14 dpdklab
2023-02-21 13:28 dpdklab
2023-02-21 13:30 dpdklab
2023-02-21 13:33 dpdklab
2023-02-21 13:36 dpdklab
2023-02-21 13:36 dpdklab
2023-02-21 13:43 dpdklab
2023-02-21 13:43 dpdklab
2023-02-21 13:52 dpdklab
2023-02-21 13:54 dpdklab
2023-02-21 14:01 dpdklab
2023-02-21 14:03 dpdklab
2023-02-21 14:05 dpdklab
2023-02-21 14:05 dpdklab
2023-02-21 16:25 dpdklab
2023-02-23 4:36 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=202302210800.31L80XLB649454@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).