automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124338 [PATCH] net/iavf: fix iavf query stats in intr thread
Date: Wed, 22 Feb 2023 12:59:49 +0800	[thread overview]
Message-ID: <202302220459.31M4xn1S1632320@localhost.localdomain> (raw)
In-Reply-To: <20230222044001.1241845-1-kaiwenx.deng@intel.com>

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

_Compilation OK_

Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Wed, 22 Feb 2023 12:40:01 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 3ba09139feabab4c0bb2e2d844c373b7c9541332

124338 --> 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-22  5:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230222044001.1241845-1-kaiwenx.deng@intel.com>
2023-02-22  4:59 ` qemudev [this message]
2023-02-22  5:03 ` qemudev
2023-02-22  5:12 ` |WARNING| " checkpatch
2023-02-22  7:39 ` |SUCCESS| " 0-day Robot
2023-02-22  5:39 dpdklab
2023-02-22  5:43 dpdklab
2023-02-22  5:43 dpdklab
2023-02-22  5:49 dpdklab
2023-02-22  5:52 dpdklab
2023-02-22  5:54 dpdklab
2023-02-22  5:55 dpdklab
2023-02-22  5:57 dpdklab
2023-02-22  6:04 dpdklab
2023-02-22  6:12 dpdklab
2023-02-22 11:01 dpdklab
2023-02-22 11:02 dpdklab
2023-02-22 11:13 dpdklab
2023-02-22 11:18 dpdklab
2023-02-22 11:20 dpdklab
2023-02-22 11:32 dpdklab
2023-02-22 11:37 dpdklab
2023-02-22 11:37 dpdklab
2023-02-22 11:39 dpdklab
2023-02-22 11:41 dpdklab
2023-02-22 11:47 dpdklab
2023-02-22 11:48 dpdklab
2023-02-22 11:50 dpdklab
2023-02-22 11:50 dpdklab
2023-02-22 14:24 dpdklab
2023-02-24  2:01 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=202302220459.31M4xn1S1632320@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).