From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139127-139134 [PATCH v2 8/8] net: clear outer UDP checksum in Intel prepare helper
Date: Fri, 5 Apr 2024 22:31:21 +0800 [thread overview]
Message-ID: <202404051431.435EVLS92980782@localhost.localdomain> (raw)
In-Reply-To: <20240405144604.906695-9-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139134
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri, 5 Apr 2024 16:45:55 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139127-139134 --> 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 14:56 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405144604.906695-9-david.marchand@redhat.com>
2024-04-05 14:31 ` qemudev [this message]
2024-04-05 14:35 ` qemudev
2024-04-05 14:48 ` |SUCCESS| pw139134 " checkpatch
2024-04-05 15:44 ` 0-day Robot
2024-04-05 18:09 ` |SUCCESS| pw139127-139134 [PATCH] [v2,8/8] net: clear outer UDP chec dpdklab
2024-04-05 18:15 ` dpdklab
2024-04-05 18:21 ` dpdklab
2024-04-05 18:22 ` dpdklab
2024-04-05 18:33 ` dpdklab
2024-04-05 18:34 ` dpdklab
2024-04-05 18:38 ` dpdklab
2024-04-05 18:40 ` dpdklab
2024-04-05 18:40 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:42 ` dpdklab
2024-04-05 18:42 ` dpdklab
2024-04-05 18:42 ` dpdklab
2024-04-05 18:43 ` dpdklab
2024-04-05 18:43 ` dpdklab
2024-04-05 18:44 ` dpdklab
2024-04-05 18:44 ` dpdklab
2024-04-05 18:45 ` dpdklab
2024-04-05 18:45 ` dpdklab
2024-04-05 18:46 ` dpdklab
2024-04-05 18:46 ` dpdklab
2024-04-05 18:46 ` dpdklab
2024-04-05 18:47 ` dpdklab
2024-04-05 18:48 ` dpdklab
2024-04-05 18:48 ` dpdklab
2024-04-05 18:48 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:49 ` dpdklab
2024-04-05 18:50 ` dpdklab
2024-04-05 18:50 ` dpdklab
2024-04-05 18:50 ` dpdklab
2024-04-05 18:50 ` dpdklab
2024-04-05 18:50 ` dpdklab
2024-04-05 18:51 ` dpdklab
2024-04-05 18:51 ` dpdklab
2024-04-05 18:52 ` dpdklab
2024-04-05 18:52 ` dpdklab
2024-04-05 18:52 ` dpdklab
2024-04-05 18:52 ` dpdklab
2024-04-05 18:52 ` dpdklab
2024-04-05 18:53 ` dpdklab
2024-04-05 18:53 ` dpdklab
2024-04-05 18:53 ` dpdklab
2024-04-05 18:56 ` dpdklab
2024-04-05 18:57 ` dpdklab
2024-04-05 18:58 ` dpdklab
2024-04-05 18:58 ` dpdklab
2024-04-05 18:59 ` dpdklab
2024-04-05 19:04 ` dpdklab
2024-04-05 19:05 ` dpdklab
2024-04-05 19:08 ` dpdklab
2024-04-05 19:09 ` dpdklab
2024-04-05 19:19 ` dpdklab
2024-04-05 19:45 ` dpdklab
2024-04-05 19:46 ` dpdklab
2024-04-05 19:46 ` dpdklab
2024-04-05 19:53 ` dpdklab
2024-04-05 19:57 ` dpdklab
2024-04-05 20:02 ` dpdklab
2024-04-05 20:21 ` dpdklab
2024-04-05 23:11 ` dpdklab
2024-04-05 23:45 ` 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=202404051431.435EVLS92980782@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).