From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124600-124602 [PATCH 5/5] app/testpmd: add error recovery usage demo
Date: Wed, 1 Mar 2023 16:07:27 +0800 [thread overview]
Message-ID: <202303010807.32187RcK951276@localhost.localdomain> (raw)
In-Reply-To: <20230301030610.49468-6-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124602
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Wed, 1 Mar 2023 03:06:06 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 4ff773385cdbd525c6e5a10015894fa26c286760
124600-124602 --> 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 prev parent reply other threads:[~2023-03-01 8:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230301030610.49468-6-fengchengwen@huawei.com>
2023-03-01 3:14 ` |SUCCESS| pw124602 " checkpatch
2023-03-01 4:59 ` 0-day Robot
2023-03-01 8:07 ` qemudev [this message]
2023-03-01 8:07 ` |SUCCESS| pw124600-124602 " qemudev
2023-03-02 3:21 |SUCCESS| pw124600-124602 [PATCH] [5/5] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 2:40 dpdklab
2023-03-02 2:35 dpdklab
2023-03-02 2:34 dpdklab
2023-03-02 2:30 dpdklab
2023-03-02 2:27 dpdklab
2023-03-02 2:27 dpdklab
2023-03-02 2:26 dpdklab
2023-03-02 2:24 dpdklab
2023-03-02 2:20 dpdklab
2023-03-02 2:13 dpdklab
2023-03-02 2:06 dpdklab
2023-03-02 2:03 dpdklab
2023-03-02 1:58 dpdklab
2023-03-02 1:45 dpdklab
2023-03-02 1:45 dpdklab
2023-03-02 1:29 dpdklab
2023-03-02 1:26 dpdklab
2023-03-01 13:20 dpdklab
2023-03-01 12:52 dpdklab
2023-03-01 12:00 dpdklab
2023-03-01 11:14 dpdklab
2023-03-01 10:39 dpdklab
2023-03-01 10:27 dpdklab
2023-03-01 10:07 dpdklab
2023-03-01 9:55 dpdklab
2023-03-01 9:01 dpdklab
2023-03-01 8:49 dpdklab
2023-03-01 8:33 dpdklab
2023-03-01 8:16 dpdklab
2023-03-01 5:20 dpdklab
2023-03-01 5:12 dpdklab
2023-03-01 5:00 dpdklab
2023-03-01 4:48 dpdklab
2023-03-01 4:48 dpdklab
2023-03-01 4:43 dpdklab
2023-03-01 4:40 dpdklab
2023-03-01 4:30 dpdklab
2023-03-01 4:29 dpdklab
2023-03-01 4:27 dpdklab
2023-03-01 4:24 dpdklab
2023-03-01 4:21 dpdklab
2023-03-01 4:21 dpdklab
2023-03-01 4:13 dpdklab
2023-03-01 4:10 dpdklab
2023-03-01 4:04 dpdklab
2023-03-01 4:01 dpdklab
2023-03-01 3:59 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=202303010807.32187RcK951276@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).