From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122745 [PATCH v2] net/sfc: export pick transfer proxy callback to representors
Date: Tue, 31 Jan 2023 19:01:58 +0800 [thread overview]
Message-ID: <202301311101.30VB1wGc3849160@localhost.localdomain> (raw)
In-Reply-To: <20230131110839.7453-1-ivan.malov@arknetworks.am>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122745
_Compilation OK_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tue, 31 Jan 2023 15:08:39 +0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 02ae4c526efd88d858d8f04fc0ef339238ef5d99
122745 --> 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-31 11:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230131110839.7453-1-ivan.malov@arknetworks.am>
2023-01-31 11:01 ` qemudev [this message]
2023-01-31 11:05 ` qemudev
2023-01-31 11:10 ` |WARNING| " checkpatch
2023-01-31 12:39 ` |SUCCESS| " 0-day Robot
2023-01-31 18:45 |SUCCESS| pw122745 [PATCH] [v2] " dpdklab
2023-01-31 19:08 dpdklab
2023-01-31 19:20 dpdklab
2023-01-31 19:21 dpdklab
2023-01-31 20:26 dpdklab
2023-01-31 20:33 dpdklab
2023-01-31 20:54 dpdklab
2023-01-31 21:01 dpdklab
2023-01-31 21:36 dpdklab
2023-02-01 5:49 dpdklab
2023-02-01 6:55 dpdklab
2023-02-01 7:34 dpdklab
2023-02-01 7:34 dpdklab
2023-02-01 7:34 dpdklab
2023-02-01 7:34 dpdklab
2023-02-01 7:46 dpdklab
2023-02-01 7:46 dpdklab
2023-02-01 7:53 dpdklab
2023-02-01 7:53 dpdklab
2023-02-01 10:50 dpdklab
2023-02-01 11:14 dpdklab
2023-02-01 13:15 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=202301311101.30VB1wGc3849160@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).