From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121450-121453 [PATCH v5 4/4] net/mlx5: fix warning about rte_memcpy length
Date: Wed, 28 Dec 2022 23:03:21 +0800 [thread overview]
Message-ID: <202212281503.2BSF3Lsh731704@localhost.localdomain> (raw)
In-Reply-To: <20221228151019.101309-4-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121453
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Wed, 28 Dec 2022 16:10:16 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 373f4c7de8ff350548cacc3d56e788461677f2c7
121450-121453 --> 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:[~2022-12-28 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221228151019.101309-4-mb@smartsharesystems.com>
2022-12-28 15:03 ` qemudev [this message]
2022-12-28 15:07 ` qemudev
2022-12-28 15:12 ` |SUCCESS| pw121453 " checkpatch
2022-12-28 16:39 ` 0-day Robot
2022-12-28 15:40 |SUCCESS| pw121450-121453 [PATCH] [v5, " dpdklab
2022-12-28 15:42 dpdklab
2022-12-28 15:45 dpdklab
2022-12-28 15:52 dpdklab
2022-12-28 15:56 dpdklab
2022-12-28 16:00 dpdklab
2022-12-28 16:21 dpdklab
2022-12-28 16:47 dpdklab
2022-12-28 16:51 dpdklab
2022-12-28 16:52 dpdklab
2022-12-28 16:58 dpdklab
2022-12-28 16:58 dpdklab
2022-12-28 16:59 dpdklab
2022-12-28 17:04 dpdklab
2022-12-28 17:06 dpdklab
2022-12-28 17:08 dpdklab
2022-12-28 17:10 dpdklab
2022-12-28 17:27 dpdklab
2022-12-28 17:31 dpdklab
2022-12-28 17:33 dpdklab
2022-12-28 17:33 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=202212281503.2BSF3Lsh731704@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).