automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125135 [PATCH v3] net/ice: fix ice dcf control thread crash
Date: Wed, 15 Mar 2023 16:14:59 +0800	[thread overview]
Message-ID: <202303150814.32F8ExGn3343721@localhost.localdomain> (raw)
In-Reply-To: <20230315082018.4260-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wed, 15 Mar 2023 08:20:18 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 743bbb1cb7e4f4c73837ab28579aaab279baa539

125135 --> 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-15  8:28 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230315082018.4260-1-mingjinx.ye@intel.com>
2023-03-15  8:14 ` qemudev [this message]
2023-03-15  8:18 ` qemudev
2023-03-15  8:26 ` checkpatch
2023-03-15 10:39 ` 0-day Robot
2023-03-18 20:57 |SUCCESS| pw125135 [PATCH] [v3] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-18 20:57 dpdklab
2023-03-18 20:56 dpdklab
2023-03-18 20:51 dpdklab
2023-03-18 20:45 dpdklab
2023-03-18 20:41 dpdklab
2023-03-18 20:40 dpdklab
2023-03-18 20:39 dpdklab
2023-03-18 20:29 dpdklab
2023-03-18 20:25 dpdklab
2023-03-18 20:23 dpdklab
2023-03-18 20:21 dpdklab
2023-03-18 20:15 dpdklab
2023-03-18 13:31 dpdklab
2023-03-18 13:31 dpdklab
2023-03-18 13:28 dpdklab
2023-03-18 13:24 dpdklab
2023-03-18 13:18 dpdklab
2023-03-18 13:16 dpdklab
2023-03-18 13:16 dpdklab
2023-03-18 13:11 dpdklab
2023-03-18 13:02 dpdklab
2023-03-18 12:59 dpdklab
2023-03-18 12:55 dpdklab
2023-03-18  7:48 dpdklab
2023-03-18  4:53 dpdklab
2023-03-18  2:06 dpdklab
2023-03-17 18:49 dpdklab
2023-03-17 13:44 dpdklab
2023-03-17 12:45 dpdklab
2023-03-15 11:52 dpdklab
2023-03-15 11:04 dpdklab
2023-03-15 11:03 dpdklab
2023-03-15 10:46 dpdklab
2023-03-15 10:45 dpdklab
2023-03-15 10:43 dpdklab
2023-03-15 10:30 dpdklab
2023-03-15 10:25 dpdklab
2023-03-15 10:13 dpdklab
2023-03-15 10:12 dpdklab
2023-03-15 10:10 dpdklab
2023-03-15 10:05 dpdklab
2023-03-15 10:01 dpdklab
2023-03-15 10:01 dpdklab
2023-03-15 10:00 dpdklab
2023-03-15  9:58 dpdklab
2023-03-15  9:56 dpdklab
2023-03-15  9:56 dpdklab
2023-03-15  9:49 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:45 dpdklab
2023-03-15  9:41 dpdklab
2023-03-15  9:41 dpdklab
2023-03-15  9:40 dpdklab
2023-03-15  9:36 dpdklab
2023-03-15  9:34 dpdklab
2023-03-15  9:34 dpdklab
2023-03-15  9:26 dpdklab
2023-03-15  9:24 dpdklab
2023-03-15  9:14 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=202303150814.32F8ExGn3343721@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).