automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124200 [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create()
Date: Tue, 21 Feb 2023 01:07:06 +0800	[thread overview]
Message-ID: <202302201707.31KH761W3806434@localhost.localdomain> (raw)
In-Reply-To: <20230220171318.1836477-1-krzysztof.karas@intel.com>

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

_Compilation OK_

Submitter: Krzysztof Karas <krzysztof.karas@intel.com>
Date: Mon, 20 Feb 2023 18:13:18 +0100
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: dce47072f58b837b11de19be412a941f556a4f06

124200 --> 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:[~2023-02-20 17:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230220171318.1836477-1-krzysztof.karas@intel.com>
2023-02-20 17:07 ` qemudev [this message]
2023-02-20 17:11 ` qemudev
2023-02-20 17:15 ` |WARNING| pw124200 [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create checkpatch
2023-02-20 19:19 ` |SUCCESS| pw124200 [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create() 0-day Robot
2023-02-20 17:46 dpdklab
2023-02-20 17:49 dpdklab
2023-02-20 17:50 dpdklab
2023-02-20 17:53 dpdklab
2023-02-20 18:01 dpdklab
2023-02-20 18:05 dpdklab
2023-02-20 18:17 dpdklab
2023-02-20 18:20 dpdklab
2023-02-20 18:33 dpdklab
2023-02-20 18:40 dpdklab
2023-02-20 20:13 dpdklab
2023-02-20 20:51 dpdklab
2023-02-20 20:52 dpdklab
2023-02-20 20:54 dpdklab
2023-02-20 21:01 dpdklab
2023-02-20 21:02 dpdklab
2023-02-20 21:04 dpdklab
2023-02-20 21:06 dpdklab
2023-02-20 21:07 dpdklab
2023-02-20 21:07 dpdklab
2023-02-20 21:09 dpdklab
2023-02-20 21:11 dpdklab
2023-02-20 21:15 dpdklab
2023-02-20 21:16 dpdklab
2023-02-21  0:13 dpdklab
2023-02-21 20:17 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=202302201707.31KH761W3806434@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).