From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124446 [PATCH v3] app/testpmd: fix secondary process not forwarding
Date: Thu, 23 Feb 2023 14:59:22 +0800 [thread overview]
Message-ID: <202302230659.31N6xMCc2763480@localhost.localdomain> (raw)
In-Reply-To: <20230223144106.707999-1-shiyangx.he@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124446
_Compilation OK_
Submitter: Shiyang He <shiyangx.he@intel.com>
Date: Thu, 23 Feb 2023 14:41:06 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 418f86c426f23ad3ffd397e69d19e8d6b5577e67
124446 --> 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-23 7:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223144106.707999-1-shiyangx.he@intel.com>
2023-02-23 6:59 ` qemudev [this message]
2023-02-23 7:03 ` qemudev
2023-02-23 7:09 ` |WARNING| " checkpatch
2023-02-23 9:59 ` |SUCCESS| " 0-day Robot
2023-02-24 23:41 |SUCCESS| pw124446 [PATCH] [v3] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 12:09 dpdklab
2023-02-23 10:39 dpdklab
2023-02-23 10:39 dpdklab
2023-02-23 10:33 dpdklab
2023-02-23 10:30 dpdklab
2023-02-23 10:29 dpdklab
2023-02-23 10:28 dpdklab
2023-02-23 10:27 dpdklab
2023-02-23 10:25 dpdklab
2023-02-23 10:22 dpdklab
2023-02-23 10:18 dpdklab
2023-02-23 10:04 dpdklab
2023-02-23 10:01 dpdklab
2023-02-23 8:02 dpdklab
2023-02-23 7:57 dpdklab
2023-02-23 7:54 dpdklab
2023-02-23 7:53 dpdklab
2023-02-23 7:50 dpdklab
2023-02-23 7:48 dpdklab
2023-02-23 7:42 dpdklab
2023-02-23 7:41 dpdklab
2023-02-23 7:37 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=202302230659.31N6xMCc2763480@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).