From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124507-124517 [PATCH v2 11/11] crypto/cnxk: add model check for pdcp chain
Date: Fri, 24 Feb 2023 17:32:23 +0800 [thread overview]
Message-ID: <202302240932.31O9WN4A3475340@localhost.localdomain> (raw)
In-Reply-To: <20230224094014.3246764-12-ktejasree@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124517
_Compilation OK_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Fri, 24 Feb 2023 15:10:04 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124507-124517 --> 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-02-24 9:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230224094014.3246764-12-ktejasree@marvell.com>
2023-02-24 9:32 ` qemudev [this message]
2023-02-24 9:36 ` qemudev
2023-02-24 9:41 ` |SUCCESS| pw124517 " checkpatch
2023-02-24 12:40 ` 0-day Robot
2023-02-24 10:09 |SUCCESS| pw124507-124517 [PATCH] [v2, " dpdklab
2023-02-24 10:13 dpdklab
2023-02-24 10:14 dpdklab
2023-02-24 10:15 dpdklab
2023-02-24 10:19 dpdklab
2023-02-24 10:21 dpdklab
2023-02-24 10:24 dpdklab
2023-02-24 10:27 dpdklab
2023-02-24 10:28 dpdklab
2023-02-24 10:34 dpdklab
2023-02-24 11:50 dpdklab
2023-02-24 11:54 dpdklab
2023-02-24 11:56 dpdklab
2023-02-24 11:59 dpdklab
2023-02-24 12:01 dpdklab
2023-02-24 12:02 dpdklab
2023-02-24 12:04 dpdklab
2023-02-24 12:08 dpdklab
2023-02-24 12:09 dpdklab
2023-02-24 12:11 dpdklab
2023-02-24 12:11 dpdklab
2023-02-24 12:13 dpdklab
2023-02-24 12:16 dpdklab
2023-02-24 12:16 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=202302240932.31O9WN4A3475340@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).