From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129287 [PATCH v2] cryptodev: fix device socket ID type
Date: Wed, 5 Jul 2023 18:27:29 +0800 [thread overview]
Message-ID: <202307051027.365ARTpb1842101@localhost.localdomain> (raw)
In-Reply-To: <20230705103630.1131136-1-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129287
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Wed, 5 Jul 2023 10:36:30 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: ddd0fe15d6bfae49c912408645b2f14e985dea27
129287 --> 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-07-05 10:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230705103630.1131136-1-ciara.power@intel.com>
2023-07-05 10:27 ` qemudev [this message]
2023-07-05 10:31 ` qemudev
2023-07-05 10:36 ` checkpatch
2023-07-05 11:59 ` 0-day Robot
2023-07-05 18:29 |SUCCESS| pw129287 [PATCH] [v2] " dpdklab
2023-07-05 18:30 dpdklab
2023-07-05 18:30 dpdklab
2023-07-05 18:34 dpdklab
2023-07-05 18:37 dpdklab
2023-07-05 19:08 dpdklab
2023-07-05 19:10 dpdklab
2023-07-05 19:20 dpdklab
2023-07-05 19:20 dpdklab
2023-07-05 19:21 dpdklab
2023-07-05 19:21 dpdklab
2023-07-05 19:27 dpdklab
2023-07-05 19:27 dpdklab
2023-07-05 19:29 dpdklab
2023-07-05 19:30 dpdklab
2023-07-05 19:30 dpdklab
2023-07-05 19:30 dpdklab
2023-07-05 19:35 dpdklab
2023-07-05 20:31 dpdklab
2023-07-05 20:40 dpdklab
2023-07-05 21:11 dpdklab
2023-07-05 21:34 dpdklab
2023-07-06 2:22 dpdklab
2023-07-07 3:53 dpdklab
2023-07-07 4:10 dpdklab
2023-07-07 4:14 dpdklab
2023-07-07 4:24 dpdklab
2023-07-07 4:55 dpdklab
2023-07-09 0:48 dpdklab
2023-07-10 16:40 dpdklab
2023-07-10 17:11 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=202307051027.365ARTpb1842101@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).