automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125257 [PATCH v2] net/idpf: cancel alarm when fail to init adapter
Date: Mon, 20 Mar 2023 15:34:38 +0800	[thread overview]
Message-ID: <202303200734.32K7Yc5K2122165@localhost.localdomain> (raw)
In-Reply-To: <20230320071219.83383-1-beilei.xing@intel.com>

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

_Compilation OK_

Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Mon, 20 Mar 2023 07:12:19 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 62e4a24aa77b267f765cf16b631e4a4ef104e365

125257 --> 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-20  7:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230320071219.83383-1-beilei.xing@intel.com>
2023-03-20  7:34 ` qemudev [this message]
2023-03-20  7:38 ` qemudev
2023-03-20  7:45 ` checkpatch
2023-03-20  9:39 ` 0-day Robot
2023-03-22 14:15 |SUCCESS| pw125257 [PATCH] [v2] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22 13:28 dpdklab
2023-03-20 21:39 dpdklab
2023-03-20 19:39 dpdklab
2023-03-20 19:38 dpdklab
2023-03-20 10:43 dpdklab
2023-03-20  9:16 dpdklab
2023-03-20  8:47 dpdklab
2023-03-20  8:41 dpdklab
2023-03-20  8:36 dpdklab
2023-03-20  8:32 dpdklab
2023-03-20  8:28 dpdklab
2023-03-20  8:28 dpdklab
2023-03-20  8:26 dpdklab
2023-03-20  8:23 dpdklab
2023-03-20  8:22 dpdklab
2023-03-20  8:20 dpdklab
2023-03-20  8:16 dpdklab
2023-03-20  8:09 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=202303200734.32K7Yc5K2122165@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).