From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138962-138963 [PATCH v2 2/2] net: stop using mmx intrinsics
Date: Thu, 28 Mar 2024 23:55:12 +0800 [thread overview]
Message-ID: <202403281555.42SFtCXT018270@localhost.localdomain> (raw)
In-Reply-To: <1711642446-6880-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138963
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thu, 28 Mar 2024 09:14:05 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
138962-138963 --> 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:[~2024-03-28 16:20 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1711642446-6880-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-28 15:55 ` qemudev [this message]
2024-03-28 15:59 ` qemudev
2024-03-28 16:14 ` |SUCCESS| pw138963 " checkpatch
2024-03-28 17:06 ` 0-day Robot
2024-03-29 0:45 ` |SUCCESS| pw138962-138963 [PATCH] [v2,2/2] net: stop using mmx intri dpdklab
2024-03-29 0:45 ` dpdklab
2024-03-29 0:45 ` dpdklab
2024-03-29 0:46 ` dpdklab
2024-03-29 0:47 ` dpdklab
2024-03-29 0:50 ` dpdklab
2024-03-29 0:54 ` dpdklab
2024-03-29 0:54 ` dpdklab
2024-03-29 0:56 ` dpdklab
2024-03-29 0:57 ` dpdklab
2024-03-29 0:59 ` dpdklab
2024-03-29 1:00 ` dpdklab
2024-03-29 1:01 ` dpdklab
2024-03-29 1:02 ` dpdklab
2024-03-29 1:04 ` dpdklab
2024-03-29 1:06 ` dpdklab
2024-03-29 1:18 ` dpdklab
2024-03-29 1:24 ` dpdklab
2024-03-29 1:26 ` dpdklab
2024-03-29 1:33 ` dpdklab
2024-03-29 1:35 ` dpdklab
2024-03-29 1:39 ` dpdklab
2024-03-29 1:45 ` dpdklab
2024-03-29 1:50 ` dpdklab
2024-03-29 1:50 ` dpdklab
2024-03-29 1:54 ` dpdklab
2024-03-29 1:56 ` dpdklab
2024-03-29 1:56 ` dpdklab
2024-03-29 1:58 ` dpdklab
2024-03-29 1:59 ` dpdklab
2024-03-29 2:01 ` dpdklab
2024-03-29 2:01 ` dpdklab
2024-03-29 2:04 ` dpdklab
2024-03-29 2:06 ` dpdklab
2024-03-29 2:08 ` dpdklab
2024-03-29 2:09 ` dpdklab
2024-03-29 2:09 ` dpdklab
2024-03-29 2:10 ` dpdklab
2024-03-29 2:11 ` dpdklab
2024-03-29 2:12 ` dpdklab
2024-03-29 2:18 ` dpdklab
2024-03-29 2:18 ` dpdklab
2024-03-29 2:19 ` dpdklab
2024-03-29 2:21 ` dpdklab
2024-03-29 2:23 ` dpdklab
2024-03-29 2:24 ` dpdklab
2024-03-29 2:24 ` dpdklab
2024-03-29 2:25 ` dpdklab
2024-03-29 2:25 ` dpdklab
2024-03-29 2:27 ` dpdklab
2024-03-29 2:27 ` dpdklab
2024-03-29 2:28 ` dpdklab
2024-03-29 2:29 ` dpdklab
2024-03-29 2:31 ` dpdklab
2024-03-29 2:31 ` dpdklab
2024-03-29 2:33 ` dpdklab
2024-03-29 2:36 ` dpdklab
2024-03-29 2:37 ` dpdklab
2024-03-29 2:37 ` dpdklab
2024-03-29 2:41 ` dpdklab
2024-03-29 2:42 ` dpdklab
2024-03-29 2:46 ` dpdklab
2024-03-29 2:47 ` dpdklab
2024-03-29 2:48 ` dpdklab
2024-03-29 2:48 ` dpdklab
2024-03-29 2:54 ` dpdklab
2024-03-29 2:55 ` dpdklab
2024-03-29 2:57 ` dpdklab
2024-03-29 2:59 ` dpdklab
2024-03-29 3:01 ` dpdklab
2024-03-29 3:05 ` dpdklab
2024-03-29 3:11 ` dpdklab
2024-03-29 3:13 ` dpdklab
2024-03-29 3:14 ` dpdklab
2024-03-29 3:17 ` dpdklab
2024-03-29 3:30 ` dpdklab
2024-03-29 3:34 ` dpdklab
2024-03-29 3:40 ` dpdklab
2024-03-29 3:45 ` dpdklab
2024-03-29 3:46 ` dpdklab
2024-03-29 3:48 ` dpdklab
2024-03-29 3:49 ` dpdklab
2024-03-29 3:52 ` dpdklab
2024-03-29 3:57 ` dpdklab
2024-03-29 4:22 ` dpdklab
2024-04-02 19:09 ` dpdklab
2024-04-02 19:13 ` dpdklab
2024-04-02 19:17 ` dpdklab
2024-04-02 19:21 ` dpdklab
2024-04-02 19:40 ` 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=202403281555.42SFtCXT018270@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).