From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137955-137959 [PATCH 5/5] net/nfp: use big-endian meta data for packet
Date: Tue, 5 Mar 2024 10:07:16 +0800 [thread overview]
Message-ID: <202403050207.42527GFd1363697@localhost.localdomain> (raw)
In-Reply-To: <20240305022923.891544-6-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137959
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tue, 5 Mar 2024 10:29:19 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 29c516fa4f5bac381825667b5bdb1ced4548c6bc
137955-137959 --> 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-05 2:32 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305022923.891544-6-chaoyong.he@corigine.com>
2024-03-05 2:07 ` qemudev [this message]
2024-03-05 2:11 ` qemudev
2024-03-05 2:30 ` |SUCCESS| pw137959 " checkpatch
2024-03-05 3:13 ` |SUCCESS| pw137955-137959 [PATCH] [5/5] net/nfp: use big-endian meta dpdklab
2024-03-05 3:13 ` dpdklab
2024-03-05 3:13 ` dpdklab
2024-03-05 3:14 ` dpdklab
2024-03-05 3:14 ` dpdklab
2024-03-05 3:14 ` dpdklab
2024-03-05 3:14 ` dpdklab
2024-03-05 3:15 ` dpdklab
2024-03-05 3:15 ` dpdklab
2024-03-05 3:15 ` dpdklab
2024-03-05 3:15 ` dpdklab
2024-03-05 3:16 ` dpdklab
2024-03-05 3:16 ` dpdklab
2024-03-05 3:16 ` dpdklab
2024-03-05 3:17 ` dpdklab
2024-03-05 3:17 ` dpdklab
2024-03-05 3:17 ` dpdklab
2024-03-05 3:18 ` dpdklab
2024-03-05 3:18 ` dpdklab
2024-03-05 3:18 ` dpdklab
2024-03-05 3:18 ` dpdklab
2024-03-05 3:19 ` dpdklab
2024-03-05 3:19 ` dpdklab
2024-03-05 3:20 ` dpdklab
2024-03-05 3:20 ` dpdklab
2024-03-05 3:20 ` dpdklab
2024-03-05 3:21 ` dpdklab
2024-03-05 3:21 ` dpdklab
2024-03-05 3:21 ` dpdklab
2024-03-05 3:22 ` dpdklab
2024-03-05 3:22 ` dpdklab
2024-03-05 3:22 ` dpdklab
2024-03-05 3:22 ` dpdklab
2024-03-05 3:22 ` dpdklab
2024-03-05 3:23 ` dpdklab
2024-03-05 3:23 ` dpdklab
2024-03-05 3:23 ` dpdklab
2024-03-05 3:24 ` dpdklab
2024-03-05 3:24 ` dpdklab
2024-03-05 3:24 ` dpdklab
2024-03-05 3:25 ` dpdklab
2024-03-05 3:25 ` |SUCCESS| pw137959 [PATCH 5/5] net/nfp: use big-endian meta data for packet 0-day Robot
2024-03-05 3:25 ` |SUCCESS| pw137955-137959 [PATCH] [5/5] net/nfp: use big-endian meta dpdklab
2024-03-05 3:25 ` dpdklab
2024-03-05 3:25 ` dpdklab
2024-03-05 3:26 ` dpdklab
2024-03-05 3:26 ` dpdklab
2024-03-05 3:26 ` dpdklab
2024-03-05 3:26 ` dpdklab
2024-03-05 3:26 ` dpdklab
2024-03-05 3:27 ` dpdklab
2024-03-05 3:27 ` dpdklab
2024-03-05 3:28 ` dpdklab
2024-03-05 3:28 ` dpdklab
2024-03-05 3:28 ` dpdklab
2024-03-05 3:28 ` dpdklab
2024-03-05 3:28 ` dpdklab
2024-03-05 3:29 ` dpdklab
2024-03-05 3:29 ` dpdklab
2024-03-05 3:30 ` dpdklab
2024-03-05 3:31 ` dpdklab
2024-03-05 3:31 ` dpdklab
2024-03-05 3:31 ` dpdklab
2024-03-05 3:32 ` dpdklab
2024-03-05 3:36 ` dpdklab
2024-03-05 3:37 ` dpdklab
2024-03-05 3:51 ` dpdklab
2024-03-05 3:53 ` dpdklab
2024-03-05 3:57 ` dpdklab
2024-03-05 4:00 ` dpdklab
2024-03-05 4:40 ` dpdklab
2024-03-08 12:30 ` dpdklab
2024-03-08 12:52 ` dpdklab
2024-03-08 13:26 ` 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=202403050207.42527GFd1363697@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).