From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130627 [PATCH] net/tap: fix L4 checksum
Date: Tue, 22 Aug 2023 15:26:10 +0800 [thread overview]
Message-ID: <202308220726.37M7QAIN1152617@localhost.localdomain> (raw)
In-Reply-To: <20230822073244.3751885-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/130627
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue, 22 Aug 2023 09:32:44 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6a5507a4511afd0203d924a08517c55b35e6e74b
130627 --> 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:[~2023-08-22 7:40 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230822073244.3751885-1-david.marchand@redhat.com>
2023-08-22 7:26 ` qemudev [this message]
2023-08-22 7:30 ` qemudev
2023-08-22 7:34 ` |WARNING| " checkpatch
2023-08-22 8:19 ` |SUCCESS| " 0-day Robot
2023-08-22 20:08 dpdklab
2023-08-22 20:09 dpdklab
2023-08-22 20:14 dpdklab
2023-08-22 20:15 dpdklab
2023-08-22 20:17 dpdklab
2023-08-22 20:25 dpdklab
2023-08-22 20:55 dpdklab
2023-08-22 20:56 dpdklab
2023-08-22 21:00 dpdklab
2023-08-22 21:01 dpdklab
2023-08-22 21:02 dpdklab
2023-08-22 21:02 dpdklab
2023-08-22 21:02 dpdklab
2023-08-22 21:02 dpdklab
2023-08-22 21:02 dpdklab
2023-08-22 21:03 dpdklab
2023-08-22 21:03 dpdklab
2023-08-22 21:03 dpdklab
2023-08-22 21:04 dpdklab
2023-08-22 21:04 dpdklab
2023-08-22 21:04 dpdklab
2023-08-22 21:04 dpdklab
2023-08-22 21:05 dpdklab
2023-08-22 21:12 dpdklab
2023-08-22 21:12 dpdklab
2023-08-22 21:13 dpdklab
2023-08-22 21:13 dpdklab
2023-08-22 21:13 dpdklab
2023-08-22 21:13 dpdklab
2023-08-22 21:15 dpdklab
2023-08-22 21:17 dpdklab
2023-08-22 21:18 dpdklab
2023-08-22 21:18 dpdklab
2023-08-22 21:19 dpdklab
2023-08-22 21:20 dpdklab
2023-08-22 21:34 dpdklab
2023-08-22 21:48 dpdklab
2023-08-22 21:49 dpdklab
2023-08-22 21:49 dpdklab
2023-08-22 21:50 dpdklab
2023-08-22 21:51 dpdklab
2023-08-22 21:51 dpdklab
2023-08-22 21:51 dpdklab
2023-08-22 21:56 dpdklab
2023-08-22 21:57 dpdklab
2023-08-22 22:00 dpdklab
2023-08-22 22:01 dpdklab
2023-08-22 22:03 dpdklab
2023-08-22 22:04 dpdklab
2023-08-22 22:05 dpdklab
2023-08-22 22:05 dpdklab
2023-08-22 22:06 dpdklab
2023-08-22 22:41 dpdklab
2023-08-23 0:51 dpdklab
2023-08-23 2:33 dpdklab
2023-08-23 8:06 dpdklab
2023-08-23 8:17 dpdklab
2023-08-23 8:20 dpdklab
2023-08-23 8:38 dpdklab
2023-08-23 8:41 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=202308220726.37M7QAIN1152617@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).