From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw127936-127938 [PATCH 3/3] net/sfc: support FEC feature
Date: Fri, 2 Jun 2023 06:12:27 +0800 [thread overview]
Message-ID: <202306012212.351MCR9n1532908@localhost.localdomain> (raw)
In-Reply-To: <20230601222349.28965-4-denis.pryazhennikov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/127938
_Compilation OK_
Submitter: Denis Pryazhennikov <denis.pryazhennikov@arknetworks.am>
Date: Fri, 2 Jun 2023 02:23:47 +0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e733c50d66ee9ffe90c8061de3f862a8a75e88c6
127936-127938 --> 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-06-01 22:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230601222349.28965-4-denis.pryazhennikov@arknetworks.am>
2023-06-01 22:12 ` qemudev [this message]
2023-06-01 22:16 ` qemudev
2023-06-01 22:24 ` |SUCCESS| pw127938 " checkpatch
2023-06-02 15:21 ` |FAILURE| " 0-day Robot
2023-06-01 22:58 |SUCCESS| pw127936-127938 [PATCH] [3/3] " dpdklab
2023-06-01 22:58 dpdklab
2023-06-01 22:59 dpdklab
2023-06-01 22:59 dpdklab
2023-06-01 23:01 dpdklab
2023-06-01 23:01 dpdklab
2023-06-01 23:07 dpdklab
2023-06-01 23:08 dpdklab
2023-06-01 23:20 dpdklab
2023-06-01 23:24 dpdklab
2023-06-01 23:28 dpdklab
2023-06-01 23:29 dpdklab
2023-06-01 23:45 dpdklab
2023-06-01 23:54 dpdklab
2023-06-08 22:03 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:31 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=202306012212.351MCR9n1532908@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).