automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123442 [PATCH] net/ice: fix ice dcf contrl thread crash
Date: Wed, 8 Feb 2023 16:36:58 +0800	[thread overview]
Message-ID: <202302080836.3188awbo1853299@localhost.localdomain> (raw)
In-Reply-To: <20230208083005.290571-1-ke1x.zhang@intel.com>

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

_Compilation OK_

Submitter: Ke Zhang <ke1x.zhang@intel.com>
Date: Wed,  8 Feb 2023 16:30:05 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: f38fdd69cef9428f04eb4297ee2f7e90ea2f40b3

123442 --> 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-08  8:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230208083005.290571-1-ke1x.zhang@intel.com>
2023-02-08  8:36 ` qemudev [this message]
2023-02-08  8:40 ` qemudev
2023-02-08  8:45 ` |WARNING| " checkpatch
2023-02-08  9:39 ` |FAILURE| " 0-day Robot
2023-02-11  4:02 |SUCCESS| " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-10 17:54 dpdklab
2023-02-10  2:25 dpdklab
2023-02-09 10:53 dpdklab
2023-02-08 18:33 dpdklab
2023-02-08 11:08 dpdklab
2023-02-08  9:50 dpdklab
2023-02-08  9:41 dpdklab
2023-02-08  9:35 dpdklab
2023-02-08  9:33 dpdklab
2023-02-08  9:29 dpdklab
2023-02-08  9:29 dpdklab
2023-02-08  9:27 dpdklab
2023-02-08  9:25 dpdklab
2023-02-08  9:21 dpdklab
2023-02-08  9:18 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=202302080836.3188awbo1853299@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).