From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125972 [PATCH v2] net/mlx5: fix lro update tcp header cksum error
Date: Thu, 13 Apr 2023 08:47:07 +0800 [thread overview]
Message-ID: <202304130047.33D0l7L42423488@localhost.localdomain> (raw)
In-Reply-To: <46433ee3531547aebf906e4144c520d1@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125972
_Compilation OK_
Submitter: jiangheng (G) <jiangheng14@huawei.com>
Date: Thu, 13 Apr 2023 00:57:36 +0000
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
125972 --> 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-04-13 1:01 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46433ee3531547aebf906e4144c520d1@huawei.com>
2023-04-13 0:47 ` qemudev [this message]
2023-04-13 0:51 ` qemudev
2023-04-13 0:58 ` |WARNING| " checkpatch
2023-04-13 2:18 ` |SUCCESS| " 0-day Robot
2023-04-13 1:22 |SUCCESS| pw125972 [PATCH] [v2] " dpdklab
2023-04-13 1:29 dpdklab
2023-04-13 1:29 dpdklab
2023-04-13 1:33 dpdklab
2023-04-13 1:33 dpdklab
2023-04-13 1:36 dpdklab
2023-04-13 1:42 dpdklab
2023-04-13 1:50 dpdklab
2023-04-13 1:51 dpdklab
2023-04-13 1:51 dpdklab
2023-04-13 1:54 dpdklab
2023-04-13 1:55 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 1:57 dpdklab
2023-04-13 1:59 dpdklab
2023-04-13 2:00 dpdklab
2023-04-13 2:03 dpdklab
2023-04-13 2:06 dpdklab
2023-04-13 2:08 dpdklab
2023-04-13 2:13 dpdklab
2023-04-13 2:14 dpdklab
2023-04-13 2:15 dpdklab
2023-04-13 2:16 dpdklab
2023-04-13 2:16 dpdklab
2023-04-13 2:17 dpdklab
2023-04-13 2:19 dpdklab
2023-04-13 2:20 dpdklab
2023-04-13 2:22 dpdklab
2023-04-13 2:23 dpdklab
2023-04-13 2:25 dpdklab
2023-04-13 2:26 dpdklab
2023-04-13 2:28 dpdklab
2023-04-13 2:37 dpdklab
2023-04-13 2:42 dpdklab
2023-04-13 2:42 dpdklab
2023-04-13 2:43 dpdklab
2023-04-13 2:44 dpdklab
2023-04-13 2:45 dpdklab
2023-04-13 2:48 dpdklab
2023-04-13 2:49 dpdklab
2023-04-13 2:49 dpdklab
2023-04-13 2:51 dpdklab
2023-04-13 2:54 dpdklab
2023-04-13 2:56 dpdklab
2023-04-13 2:56 dpdklab
2023-04-13 2:57 dpdklab
2023-04-13 3:04 dpdklab
2023-04-13 3:06 dpdklab
2023-04-13 3:09 dpdklab
2023-04-13 3:13 dpdklab
2023-04-13 3:14 dpdklab
2023-04-13 3:16 dpdklab
2023-04-13 3:18 dpdklab
2023-04-13 3:18 dpdklab
2023-04-13 6:19 dpdklab
2023-04-13 6:19 dpdklab
2023-04-13 7:23 dpdklab
2023-04-13 7:23 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=202304130047.33D0l7L42423488@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).