From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122607 [PATCH] app/testpmd: fix link check condition on port start
Date: Sat, 28 Jan 2023 06:37:00 +0800 [thread overview]
Message-ID: <202301272237.30RMb0e31932813@localhost.localdomain> (raw)
In-Reply-To: <20230127224514.2650827-1-ferruh.yigit@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122607
_Compilation OK_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Fri, 27 Jan 2023 22:45:13 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: aeae386262502f02fd91970d8aba246c29b46a69
122607 --> 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-01-27 22:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230127224514.2650827-1-ferruh.yigit@amd.com>
2023-01-27 22:37 ` qemudev [this message]
2023-01-27 22:40 ` qemudev
2023-01-27 22:45 ` checkpatch
2023-01-27 23:39 ` 0-day Robot
2023-02-17 10:26 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 9:15 dpdklab
2023-02-15 23:38 dpdklab
2023-02-15 23:38 dpdklab
2023-02-15 23:36 dpdklab
2023-02-15 23:33 dpdklab
2023-02-15 23:32 dpdklab
2023-02-15 23:27 dpdklab
2023-02-15 23:20 dpdklab
2023-02-15 23:19 dpdklab
2023-02-15 23:19 dpdklab
2023-02-15 23:15 dpdklab
2023-02-15 23:13 dpdklab
2023-02-15 23:13 dpdklab
2023-02-15 23:05 dpdklab
2023-02-15 23:05 dpdklab
2023-02-15 23:04 dpdklab
2023-02-15 23:03 dpdklab
2023-02-15 23:01 dpdklab
2023-02-15 22:58 dpdklab
2023-02-15 22:58 dpdklab
2023-02-15 22:56 dpdklab
2023-02-15 22:53 dpdklab
2023-02-15 22:49 dpdklab
2023-02-15 22:48 dpdklab
2023-02-15 22:45 dpdklab
2023-02-15 22:40 dpdklab
2023-02-15 22:33 dpdklab
2023-02-15 22:29 dpdklab
2023-02-15 22:07 dpdklab
2023-01-28 2:38 dpdklab
2023-01-28 2:38 dpdklab
2023-01-28 2:38 dpdklab
2023-01-28 2:37 dpdklab
2023-01-28 2:37 dpdklab
2023-01-28 2:33 dpdklab
2023-01-28 2:32 dpdklab
2023-01-28 2:32 dpdklab
2023-01-28 2:32 dpdklab
2023-01-28 2:26 dpdklab
2023-01-28 2:15 dpdklab
2023-01-28 2:15 dpdklab
2023-01-28 1:23 dpdklab
2023-01-28 0:33 dpdklab
2023-01-28 0:02 dpdklab
2023-01-27 23:30 dpdklab
2023-01-27 23:26 dpdklab
2023-01-27 23:23 dpdklab
2023-01-27 23:21 dpdklab
2023-01-27 23:19 dpdklab
2023-01-27 23:17 dpdklab
2023-01-27 23:10 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=202301272237.30RMb0e31932813@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).