automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138119 [PATCH] crypto/qat: fix ccm null aad pointer segfault
Date: Fri, 8 Mar 2024 16:05:44 +0800	[thread overview]
Message-ID: <202403080805.42885imx884231@localhost.localdomain> (raw)
In-Reply-To: <20240308082512.5226-1-arkadiuszx.kusztal@intel.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138119

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Fri,  8 Mar 2024 08:25:12 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 4877d26a37d3bb515fc714b260066c0cac1985cf

138119 --> 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


       reply	other threads:[~2024-03-08  8:30 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308082512.5226-1-arkadiuszx.kusztal@intel.com>
2024-03-08  8:05 ` qemudev [this message]
2024-03-08  8:10 ` qemudev
2024-03-08  8:26 ` checkpatch
2024-03-08  9:24 ` 0-day Robot
2024-03-08 10:56 ` |SUCCESS| pw138119 [PATCH] crypto/qat: fix ccm null aad pointer segf dpdklab
2024-03-08 10:58 ` dpdklab
2024-03-08 11:04 ` dpdklab
2024-03-08 11:05 ` dpdklab
2024-03-08 11:23 ` dpdklab
2024-03-08 11:23 ` dpdklab
2024-03-08 11:24 ` dpdklab
2024-03-08 11:25 ` dpdklab
2024-03-08 11:25 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:28 ` dpdklab
2024-03-08 11:31 ` dpdklab
2024-03-08 11:32 ` dpdklab
2024-03-08 11:32 ` dpdklab
2024-03-08 11:36 ` dpdklab
2024-03-08 11:36 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:38 ` dpdklab
2024-03-08 11:38 ` |FAILURE| " dpdklab
2024-03-08 11:38 ` |SUCCESS| " dpdklab
2024-03-08 11:38 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` |FAILURE| " dpdklab
2024-03-08 11:41 ` |SUCCESS| " dpdklab
2024-03-08 11:41 ` |FAILURE| " dpdklab
2024-03-08 11:41 ` |SUCCESS| " dpdklab
2024-03-08 11:42 ` dpdklab
2024-03-08 11:42 ` |FAILURE| " dpdklab
2024-03-08 11:42 ` |SUCCESS| " dpdklab
2024-03-08 11:42 ` |FAILURE| " dpdklab
2024-03-08 11:42 ` |SUCCESS| " dpdklab
2024-03-08 11:43 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` |FAILURE| " dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:47 ` |SUCCESS| " dpdklab
2024-03-08 11:47 ` dpdklab
2024-03-08 11:48 ` |FAILURE| " dpdklab
2024-03-08 11:50 ` |SUCCESS| " dpdklab
2024-03-08 11:53 ` |FAILURE| " dpdklab
2024-03-08 12:12 ` dpdklab
2024-03-08 12:13 ` |SUCCESS| " dpdklab
2024-03-08 12:38 ` dpdklab
2024-03-08 12:59 ` dpdklab
2024-03-08 12:59 ` dpdklab
2024-03-08 13:11 ` dpdklab
2024-03-08 13:20 ` dpdklab
2024-03-08 13:23 ` dpdklab
2024-03-08 13:55 ` dpdklab
2024-03-13  1:26 ` dpdklab
2024-03-13  2:02 ` 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=202403080805.42885imx884231@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).