automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125410 [PATCH v6] net/ice: fix ice dcf control thread crash
Date: Thu, 23 Mar 2023 14:20:07 +0800	[thread overview]
Message-ID: <202303230620.32N6K7jI503484@localhost.localdomain> (raw)
In-Reply-To: <20230322055606.84874-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wed, 22 Mar 2023 05:56:06 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 0a0ab32ee0a4002ef88b93b111a2be597040391e

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


  parent reply	other threads:[~2023-03-23  6:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230322055606.84874-1-mingjinx.ye@intel.com>
2023-03-22  6:01 ` checkpatch
2023-03-22  8:19 ` 0-day Robot
2023-03-23  6:20 ` qemudev [this message]
2023-03-23  6:20 ` qemudev
2023-03-24 10:54 |SUCCESS| pw125410 [PATCH] [v6] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-23 14:59 dpdklab
2023-03-23  9:31 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22  7:29 dpdklab
2023-03-22  7:02 dpdklab
2023-03-22  6:58 dpdklab
2023-03-22  6:53 dpdklab
2023-03-22  6:49 dpdklab
2023-03-22  6:49 dpdklab
2023-03-22  6:43 dpdklab
2023-03-22  6:41 dpdklab
2023-03-22  6:41 dpdklab
2023-03-22  6:39 dpdklab
2023-03-22  6:36 dpdklab
2023-03-22  6:34 dpdklab
2023-03-22  6:30 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=202303230620.32N6K7jI503484@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).