From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125087 [PATCH] net/i4oe: fix MAC loopback on X722
Date: Wed, 15 Mar 2023 08:53:27 +0800 [thread overview]
Message-ID: <202303150053.32F0rRgQ3172850@localhost.localdomain> (raw)
In-Reply-To: <20230314030544.6664-1-wenjing.qiao@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125087
_Compilation OK_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Mon, 13 Mar 2023 23:05:44 -0400
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 743bbb1cb7e4f4c73837ab28579aaab279baa539
125087 --> 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-15 1:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230314030544.6664-1-wenjing.qiao@intel.com>
2023-03-14 3:11 ` checkpatch
2023-03-15 0:53 ` qemudev [this message]
2023-03-15 0:53 ` qemudev
2023-03-16 3:24 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 7:07 dpdklab
2023-03-15 7:06 dpdklab
2023-03-15 7:06 dpdklab
2023-03-15 7:00 dpdklab
2023-03-15 6:53 dpdklab
2023-03-15 6:49 dpdklab
2023-03-15 6:45 dpdklab
2023-03-15 6:40 dpdklab
2023-03-15 6:39 dpdklab
2023-03-15 6:31 dpdklab
2023-03-15 6:26 dpdklab
2023-03-15 6:23 dpdklab
2023-03-15 6:22 dpdklab
2023-03-15 6:17 dpdklab
2023-03-14 16:04 dpdklab
2023-03-14 15:47 dpdklab
2023-03-14 6:28 dpdklab
2023-03-14 6:25 dpdklab
2023-03-14 6:12 dpdklab
2023-03-14 6:11 dpdklab
2023-03-14 6:03 dpdklab
2023-03-14 5:58 dpdklab
2023-03-14 5:55 dpdklab
2023-03-14 5:54 dpdklab
2023-03-14 5:52 dpdklab
2023-03-14 5:48 dpdklab
2023-03-14 5:42 dpdklab
2023-03-14 5:41 dpdklab
2023-03-14 5:36 dpdklab
2023-03-14 5: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=202303150053.32F0rRgQ3172850@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).