From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120128 [PATCH v1] crypto/ccp: bug fixes for ccp device probe flow
Date: Thu, 24 Nov 2022 21:50:00 +0800 [thread overview]
Message-ID: <202211241350.2AODo0A31187285@localhost.localdomain> (raw)
In-Reply-To: <20221124135645.5955-1-sunilprakashrao.uttarwar@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120128
_Compilation OK_
Submitter: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>
Date: Thu, 24 Nov 2022 19:26:45 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 84f8e7c029b04fa43d0982e4af593257316798cb
120128 --> 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-11-24 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221124135645.5955-1-sunilprakashrao.uttarwar@amd.com>
2022-11-24 13:50 ` qemudev [this message]
2022-11-24 13:53 ` qemudev
2022-11-24 13:58 ` checkpatch
2022-11-24 14:59 ` 0-day Robot
2022-11-24 16:17 |SUCCESS| pw120128 [PATCH] [v1] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-11-24 15:30 dpdklab
2022-11-24 15:13 dpdklab
2022-11-24 14:55 dpdklab
2022-11-24 14:49 dpdklab
2022-11-24 14:44 dpdklab
2022-11-24 14:42 dpdklab
2022-11-24 14:41 dpdklab
2022-11-24 14:35 dpdklab
2022-11-24 14:30 dpdklab
2022-11-24 14:29 dpdklab
2022-11-24 14:28 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=202211241350.2AODo0A31187285@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).