automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125057-125058 [PATCH 2/2] common/cnxk: fix SPI to SA index destroy
Date: Mon, 13 Mar 2023 13:13:03 +0800	[thread overview]
Message-ID: <202303130513.32D5D3xW104103@localhost.localdomain> (raw)
In-Reply-To: <20230313052403.230953-2-psatheesh@marvell.com>

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

_Compilation OK_

Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Mon, 13 Mar 2023 10:54:02 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: for-next-net
  CommitID: 4352a3bcee3a4cc20c8accb71d683d5add3c6f80

125057-125058 --> 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-03-13  5:26 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230313052403.230953-2-psatheesh@marvell.com>
2023-03-13  5:13 ` qemudev [this message]
2023-03-13  5:16 ` qemudev
2023-03-13  5:25 ` |SUCCESS| pw125058 " checkpatch
2023-03-13  7:19 ` |SUCCESS| pw125058 [dpdk-dev] " 0-day Robot
2023-03-13  6:13 |SUCCESS| pw125057-125058 [PATCH] [2/2] " dpdklab
2023-03-13  6:15 dpdklab
2023-03-13  6:19 dpdklab
2023-03-13  6:25 dpdklab
2023-03-13  6:27 dpdklab
2023-03-13  6:30 dpdklab
2023-03-13  6:31 dpdklab
2023-03-13  6:34 dpdklab
2023-03-13  6:35 dpdklab
2023-03-13  6:40 dpdklab
2023-03-13  6:44 dpdklab
2023-03-13  6:44 dpdklab
2023-03-13  6:50 dpdklab
2023-03-13  6:56 dpdklab
2023-03-13  6:56 dpdklab
2023-03-13  6:57 dpdklab
2023-03-13  6:58 dpdklab
2023-03-13  7:00 dpdklab
2023-03-13  7:04 dpdklab
2023-03-13  7:04 dpdklab
2023-03-13  7:05 dpdklab
2023-03-13  7:10 dpdklab
2023-03-13  7:12 dpdklab
2023-03-13  7:16 dpdklab
2023-03-13  8:03 dpdklab
2023-03-13  8:19 dpdklab
2023-03-13  9:38 dpdklab
2023-03-13 10:31 dpdklab
2023-03-13 17:58 dpdklab
2023-03-13 18:12 dpdklab
2023-03-13 18:20 dpdklab
2023-03-13 18:36 dpdklab
2023-03-13 18:49 dpdklab
2023-03-13 18:49 dpdklab
2023-03-13 18:52 dpdklab
2023-03-13 18:54 dpdklab
2023-03-13 18:56 dpdklab
2023-03-13 18:57 dpdklab
2023-03-13 18:58 dpdklab
2023-03-13 19:33 dpdklab
2023-03-13 19:34 dpdklab
2023-03-13 19:45 dpdklab
2023-03-13 19:45 dpdklab
2023-03-13 19:46 dpdklab
2023-03-13 19:53 dpdklab
2023-03-13 20:00 dpdklab
2023-03-13 20:06 dpdklab
2023-03-13 20:11 dpdklab
2023-03-13 20:12 dpdklab
2023-03-13 20:14 dpdklab
2023-03-13 20:15 dpdklab
2023-03-13 20:19 dpdklab
2023-03-13 20:21 dpdklab
2023-03-13 20:55 dpdklab
2023-03-13 20:56 dpdklab
2023-03-14 15:30 dpdklab
2023-03-14 16:53 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=202303130513.32D5D3xW104103@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).