From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151184-151215 [PATCH 32/32] test/cryptodev: replace memcpy with structure assignment
Date: Sun, 9 Feb 2025 04:09:41 +0800 [thread overview]
Message-ID: <202502082009.518K9fh71981954@localhost.localdomain> (raw)
In-Reply-To: <20250208203142.242284-33-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/151215
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sat, 8 Feb 2025 12:21:53 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3553897d84d8b54a1b1136cbf04dd7f1a40fd85b
151184-151215 --> 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:[~2025-02-08 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250208203142.242284-33-stephen@networkplumber.org>
2025-02-08 20:09 ` qemudev [this message]
2025-02-08 20:14 ` qemudev
2025-02-08 20:36 ` |SUCCESS| pw151215 " checkpatch
2025-02-08 21:09 ` |PENDING| pw151184-151215 [PATCH] [32/32] test/cryptodev: replace me dpdklab
2025-02-08 21:12 ` dpdklab
2025-02-08 21:13 ` dpdklab
2025-02-08 21:15 ` dpdklab
2025-02-08 21:17 ` |SUCCESS| " dpdklab
2025-02-08 21:17 ` dpdklab
2025-02-08 21:24 ` |SUCCESS| pw151215 [PATCH 32/32] test/cryptodev: replace memcpy with structure assignment 0-day Robot
2025-02-08 21:30 ` |SUCCESS| pw151184-151215 [PATCH] [32/32] test/cryptodev: replace me dpdklab
2025-02-08 21:37 ` dpdklab
2025-02-08 21:42 ` dpdklab
2025-02-08 21:49 ` dpdklab
2025-02-08 21:50 ` dpdklab
2025-02-08 21:52 ` dpdklab
2025-02-08 21:58 ` dpdklab
2025-02-08 22:12 ` dpdklab
2025-02-08 22:39 ` 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=202502082009.518K9fh71981954@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).