From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126079 [PATCH] crypto/qat: fix stack buffer overflow in SGL loop
Date: Fri, 14 Apr 2023 20:44:25 +0800 [thread overview]
Message-ID: <202304141244.33ECiPYb1478059@localhost.localdomain> (raw)
In-Reply-To: <20230414123131.575412-1-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126079
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Fri, 14 Apr 2023 12:31:31 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
126079 --> 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 prev parent reply other threads:[~2023-04-14 12:58 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414123131.575412-1-ciara.power@intel.com>
2023-04-14 12:33 ` checkpatch
2023-04-14 12:44 ` qemudev [this message]
2023-04-14 12:48 ` qemudev
2023-04-14 13:39 ` 0-day Robot
2023-04-14 20:39 dpdklab
2023-04-14 20:46 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:48 dpdklab
2023-04-14 21:00 dpdklab
2023-04-14 21:16 dpdklab
2023-04-14 21:24 dpdklab
2023-04-14 22:17 dpdklab
2023-04-14 22:20 dpdklab
2023-04-14 22:24 dpdklab
2023-04-14 22:25 dpdklab
2023-04-14 22:26 dpdklab
2023-04-14 22:28 dpdklab
2023-04-14 22:30 dpdklab
2023-04-14 22:32 dpdklab
2023-04-14 22:33 dpdklab
2023-04-14 22:40 dpdklab
2023-04-14 22:44 dpdklab
2023-04-14 22:45 dpdklab
2023-04-14 22:55 dpdklab
2023-04-14 23:11 dpdklab
2023-04-14 23:13 dpdklab
2023-04-14 23:15 dpdklab
2023-04-14 23:15 dpdklab
2023-04-14 23:17 dpdklab
2023-04-14 23:19 dpdklab
2023-04-14 23:22 dpdklab
2023-04-14 23:33 dpdklab
2023-04-14 23:39 dpdklab
2023-04-14 23:51 dpdklab
2023-04-14 23:52 dpdklab
2023-04-14 23:52 dpdklab
2023-04-14 23:55 dpdklab
2023-04-15 0:00 dpdklab
2023-04-15 0:01 dpdklab
2023-04-15 0:14 dpdklab
2023-04-15 0:15 dpdklab
2023-04-15 4:06 dpdklab
2023-04-15 5:30 dpdklab
2023-04-15 5:42 dpdklab
2023-04-15 5:47 dpdklab
2023-04-15 6:03 dpdklab
2023-04-15 6:07 dpdklab
2023-04-15 6:12 dpdklab
2023-04-15 7:00 dpdklab
2023-04-15 7:32 dpdklab
2023-04-15 10:11 dpdklab
2023-04-15 10:12 dpdklab
2023-04-15 10:45 dpdklab
2023-04-15 10:46 dpdklab
2023-04-18 16:48 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=202304141244.33ECiPYb1478059@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).