From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139118-139125 [PATCH 8/8] net: clear outer UDP checksum in Intel prepare helper
Date: Fri, 5 Apr 2024 20:30:29 +0800 [thread overview]
Message-ID: <202404051230.435CUTEx2850560@localhost.localdomain> (raw)
In-Reply-To: <20240405125039.897933-9-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139125
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri, 5 Apr 2024 14:49:40 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139118-139125 --> 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-05 12:55 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405125039.897933-9-david.marchand@redhat.com>
2024-04-05 12:30 ` qemudev [this message]
2024-04-05 12:34 ` qemudev
2024-04-05 12:54 ` |SUCCESS| pw139125 " checkpatch
2024-04-05 13:44 ` 0-day Robot
2024-04-05 15:23 ` |SUCCESS| pw139118-139125 [PATCH] [8/8] net: clear outer UDP checksu dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:25 ` dpdklab
2024-04-05 15:25 ` dpdklab
2024-04-05 15:30 ` dpdklab
2024-04-05 15:32 ` dpdklab
2024-04-05 15:33 ` dpdklab
2024-04-05 15:34 ` dpdklab
2024-04-05 15:50 ` dpdklab
2024-04-05 15:51 ` dpdklab
2024-04-05 15:54 ` dpdklab
2024-04-05 15:56 ` dpdklab
2024-04-05 15:56 ` dpdklab
2024-04-05 15:56 ` dpdklab
2024-04-05 15:57 ` dpdklab
2024-04-05 15:57 ` dpdklab
2024-04-05 15:57 ` dpdklab
2024-04-05 15:58 ` dpdklab
2024-04-05 15:58 ` dpdklab
2024-04-05 15:58 ` dpdklab
2024-04-05 15:58 ` dpdklab
2024-04-05 15:59 ` dpdklab
2024-04-05 15:59 ` dpdklab
2024-04-05 15:59 ` dpdklab
2024-04-05 15:59 ` dpdklab
2024-04-05 16:00 ` dpdklab
2024-04-05 16:00 ` dpdklab
2024-04-05 16:00 ` dpdklab
2024-04-05 16:01 ` dpdklab
2024-04-05 16:01 ` dpdklab
2024-04-05 16:01 ` dpdklab
2024-04-05 16:02 ` dpdklab
2024-04-05 16:02 ` dpdklab
2024-04-05 16:02 ` dpdklab
2024-04-05 16:03 ` dpdklab
2024-04-05 16:03 ` dpdklab
2024-04-05 16:03 ` dpdklab
2024-04-05 16:04 ` dpdklab
2024-04-05 16:04 ` dpdklab
2024-04-05 16:04 ` dpdklab
2024-04-05 16:05 ` dpdklab
2024-04-05 16:05 ` dpdklab
2024-04-05 16:05 ` dpdklab
2024-04-05 16:05 ` dpdklab
2024-04-05 16:06 ` dpdklab
2024-04-05 16:06 ` dpdklab
2024-04-05 16:06 ` dpdklab
2024-04-05 16:06 ` dpdklab
2024-04-05 16:07 ` dpdklab
2024-04-05 16:07 ` dpdklab
2024-04-05 16:07 ` dpdklab
2024-04-05 16:07 ` dpdklab
2024-04-05 16:07 ` dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:09 ` dpdklab
2024-04-05 16:10 ` dpdklab
2024-04-05 16:10 ` dpdklab
2024-04-05 16:10 ` dpdklab
2024-04-05 16:10 ` dpdklab
2024-04-05 16:10 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:11 ` dpdklab
2024-04-05 16:13 ` dpdklab
2024-04-05 16:13 ` dpdklab
2024-04-05 16:14 ` dpdklab
2024-04-05 16:14 ` dpdklab
2024-04-05 16:16 ` dpdklab
2024-04-05 16:19 ` dpdklab
2024-04-05 16:20 ` dpdklab
2024-04-05 16:20 ` dpdklab
2024-04-05 16:29 ` dpdklab
2024-04-05 16:38 ` dpdklab
2024-04-05 16:39 ` dpdklab
2024-04-05 16:43 ` dpdklab
2024-04-05 17:21 ` dpdklab
2024-04-05 18:51 ` dpdklab
2024-04-05 18:52 ` 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=202404051230.435CUTEx2850560@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).