From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139436-139437 [RFC 2/2] ethdev: add data size field to GENEVE option item
Date: Wed, 17 Apr 2024 15:00:07 +0800 [thread overview]
Message-ID: <202404170700.43H707bB3453173@localhost.localdomain> (raw)
In-Reply-To: <20240417072304.3260172-3-michaelba@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139437
_Compilation OK_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Wed, 17 Apr 2024 10:23:03 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6db5f91b5e628671c341b833f21ea35e65e9699d
139436-139437 --> 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-04-17 7:25 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417072304.3260172-3-michaelba@nvidia.com>
2024-04-17 7:00 ` qemudev [this message]
2024-04-17 7:04 ` qemudev
2024-04-17 7:24 ` |SUCCESS| pw139437 " checkpatch
2024-04-17 8:24 ` 0-day Robot
2024-04-17 10:22 ` |SUCCESS| pw139436-139437 [PATCH] [RFC,2/2] ethdev: add data size fi dpdklab
2024-04-17 10:23 ` dpdklab
2024-04-17 10:38 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:43 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:49 ` dpdklab
2024-04-17 10:49 ` dpdklab
2024-04-17 10:50 ` dpdklab
2024-04-17 10:51 ` dpdklab
2024-04-17 10:52 ` dpdklab
2024-04-17 10:52 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:07 ` dpdklab
2024-04-17 11:07 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:41 ` dpdklab
2024-04-17 11:41 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:43 ` dpdklab
2024-04-17 11:44 ` dpdklab
2024-04-17 11:44 ` dpdklab
2024-04-17 11:45 ` dpdklab
2024-04-17 11:45 ` dpdklab
2024-04-17 11:45 ` dpdklab
2024-04-17 11:45 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:48 ` dpdklab
2024-04-17 11:48 ` dpdklab
2024-04-17 11:49 ` dpdklab
2024-04-17 11:51 ` dpdklab
2024-04-17 11:52 ` dpdklab
2024-04-17 11:52 ` dpdklab
2024-04-17 11:53 ` dpdklab
2024-04-17 11:55 ` dpdklab
2024-04-17 11:55 ` dpdklab
2024-04-17 11:56 ` dpdklab
2024-04-17 11:56 ` dpdklab
2024-04-17 11:57 ` dpdklab
2024-04-17 11:59 ` dpdklab
2024-04-17 12:00 ` dpdklab
2024-04-17 12:01 ` dpdklab
2024-04-17 12:04 ` dpdklab
2024-04-17 12:04 ` dpdklab
2024-04-17 12:04 ` dpdklab
2024-04-17 12:06 ` dpdklab
2024-04-17 12:07 ` dpdklab
2024-04-17 12:09 ` dpdklab
2024-04-17 12:09 ` dpdklab
2024-04-17 12:09 ` dpdklab
2024-04-17 12:12 ` dpdklab
2024-04-17 12:14 ` dpdklab
2024-04-17 12:15 ` dpdklab
2024-04-17 12:24 ` dpdklab
2024-04-17 12:28 ` dpdklab
2024-04-17 12:32 ` dpdklab
2024-04-17 12:33 ` dpdklab
2024-04-17 12:36 ` dpdklab
2024-04-17 12:48 ` dpdklab
2024-04-17 12:55 ` dpdklab
2024-04-17 13:25 ` dpdklab
2024-04-17 13:38 ` dpdklab
2024-04-17 13:39 ` dpdklab
2024-04-17 13:40 ` dpdklab
2024-04-17 13:41 ` dpdklab
2024-04-17 13:53 ` dpdklab
2024-04-17 14:47 ` 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=202404170700.43H707bB3453173@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).