From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122945-122950 [PATCH v6 8/8] net: mark all big endian types
Date: Fri, 3 Feb 2023 18:32:55 +0800 [thread overview]
Message-ID: <202302031032.313AWtd51719439@localhost.localdomain> (raw)
In-Reply-To: <20230202124500.2578857-9-ferruh.yigit@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122950
_Compilation OK_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Thu, 2 Feb 2023 12:44:53 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8865a5a6e68b54c298987f07d2604c62eda8bffd
122945-122950 --> 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-02-03 10:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230202124500.2578857-9-ferruh.yigit@amd.com>
2023-02-02 12:47 ` |SUCCESS| pw122950 " checkpatch
2023-02-02 14:59 ` 0-day Robot
2023-02-03 10:32 ` qemudev [this message]
2023-02-03 10:36 ` |SUCCESS| pw122945-122950 " qemudev
2023-02-04 12:57 |SUCCESS| pw122945-122950 [PATCH] [v6, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-04 9:01 dpdklab
2023-02-04 1:52 dpdklab
2023-02-03 6:32 dpdklab
2023-02-03 6:32 dpdklab
2023-02-03 6:31 dpdklab
2023-02-03 6:31 dpdklab
2023-02-03 6:31 dpdklab
2023-02-03 6:31 dpdklab
2023-02-03 5:19 dpdklab
2023-02-02 16:03 dpdklab
2023-02-02 13:32 dpdklab
2023-02-02 13:27 dpdklab
2023-02-02 13:18 dpdklab
2023-02-02 13:16 dpdklab
2023-02-02 13:14 dpdklab
2023-02-02 13:12 dpdklab
2023-02-02 13:11 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=202302031032.313AWtd51719439@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).