From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125859 [PATCH 1/1] net/ixgbe: add a proper memory barrier for LoongArch
Date: Fri, 7 Apr 2023 16:47:08 +0800 [thread overview]
Message-ID: <202304070847.3378l8hj2795917@localhost.localdomain> (raw)
In-Reply-To: <20230407085041.3966259-1-zhoumin@loongson.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125859
_Compilation OK_
Submitter: Min Zhou <zhoumin@loongson.cn>
Date: Fri, 7 Apr 2023 16:50:41 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 3bc3d9f9f3df2e22c3958d1a3dac68ce2d708b33
125859 --> 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-04-07 9:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230407085041.3966259-1-zhoumin@loongson.cn>
2023-04-07 8:47 ` qemudev [this message]
2023-04-07 8:51 ` qemudev
2023-04-07 8:51 ` checkpatch
2023-04-07 9:59 ` 0-day Robot
2023-04-07 13:59 |SUCCESS| pw125859 [PATCH] [1/1] " dpdklab
2023-04-07 14:01 dpdklab
2023-04-07 14:04 dpdklab
2023-04-07 14:07 dpdklab
2023-04-07 14:08 dpdklab
2023-04-07 14:09 dpdklab
2023-04-07 14:10 dpdklab
2023-04-07 14:10 dpdklab
2023-04-07 14:11 dpdklab
2023-04-07 14:11 dpdklab
2023-04-07 14:15 dpdklab
2023-04-07 14:15 dpdklab
2023-04-07 14:16 dpdklab
2023-04-07 14:19 dpdklab
2023-04-07 14:23 dpdklab
2023-04-07 14:24 dpdklab
2023-04-07 14:28 dpdklab
2023-04-07 14:32 dpdklab
2023-04-07 14:33 dpdklab
2023-04-07 14:33 dpdklab
2023-04-07 14:35 dpdklab
2023-04-07 14:37 dpdklab
2023-04-07 14:41 dpdklab
2023-04-07 14:42 dpdklab
2023-04-07 14:43 dpdklab
2023-04-07 14:44 dpdklab
2023-04-07 14:50 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=202304070847.3378l8hj2795917@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).