automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121467 [PATCH v3] kni: fix possible alloc_q starvation when mbufs are exhausted
Date: Fri, 30 Dec 2022 12:17:44 +0800	[thread overview]
Message-ID: <202212300417.2BU4Hiee1032048@localhost.localdomain> (raw)
In-Reply-To: <20221230042338.1670768-1-zhouyates@gmail.com>

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

_Compilation OK_

Submitter: Yangchao Zhou <zhouyates@gmail.com>
Date: Fri, 30 Dec 2022 12:23:38 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 9351bc0906b4585fd9d50a89f9f6d2f091d3e822

121467 --> 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:[~2022-12-30  4:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221230042338.1670768-1-zhouyates@gmail.com>
2022-12-30  4:17 ` qemudev [this message]
2022-12-30  4:21 ` qemudev
2022-12-30  4:26 ` checkpatch
2022-12-30  5:19 ` 0-day Robot
2022-12-30  4:49 |SUCCESS| pw121467 [PATCH] [v3] " dpdklab
2022-12-30  4:49 dpdklab
2022-12-30  4:53 dpdklab
2022-12-30  5:02 dpdklab
2022-12-30  5:05 dpdklab
2022-12-30  5:09 dpdklab
2022-12-30  5:31 dpdklab
2022-12-30  5:46 dpdklab
2022-12-30  6:26 dpdklab
2022-12-30  6:46 dpdklab
2022-12-30  6:58 dpdklab
2022-12-30  7:08 dpdklab
2022-12-30  7:08 dpdklab
2022-12-30  7:08 dpdklab
2022-12-30  7:09 dpdklab
2022-12-30  7:11 dpdklab
2022-12-30  7:11 dpdklab
2022-12-30  7:12 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=202212300417.2BU4Hiee1032048@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).