automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125247-125248 [PATCH 2/2] net/mana: optimize completion queue polling by processing a batch at a time
Date: Sat, 18 Mar 2023 07:21:32 +0800	[thread overview]
Message-ID: <202303172321.32HNLWfI1664873@localhost.localdomain> (raw)
In-Reply-To: <1679095964-18532-2-git-send-email-longli@linuxonhyperv.com>

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

_Compilation OK_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Fri, 17 Mar 2023 16:32:43 -0700
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 8880c07e04820eba0692cadb8764d1bbd09751a5

125247-125248 --> 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-17 23:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1679095964-18532-2-git-send-email-longli@linuxonhyperv.com>
2023-03-17 23:21 ` qemudev [this message]
2023-03-17 23:25 ` qemudev
2023-03-17 23:33 ` |WARNING| pw125248 " checkpatch
2023-03-18  1:59 ` |SUCCESS| " 0-day Robot
2023-03-22  8:33 |SUCCESS| pw125247-125248 [PATCH] [2/2] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  8:28 dpdklab
2023-03-22  5:43 dpdklab
2023-03-22  5:43 dpdklab
2023-03-22  4:35 dpdklab
2023-03-22  4:33 dpdklab
2023-03-20 20:26 dpdklab
2023-03-20 20:20 dpdklab
2023-03-20 19:16 dpdklab
2023-03-20 12:07 dpdklab
2023-03-20 10:42 dpdklab
2023-03-20  0:59 dpdklab
2023-03-20  0:54 dpdklab
2023-03-20  0:50 dpdklab
2023-03-20  0:35 dpdklab
2023-03-20  0:29 dpdklab
2023-03-20  0:25 dpdklab
2023-03-19 17:09 dpdklab
2023-03-19 16:39 dpdklab
2023-03-18  1:26 dpdklab
2023-03-18  1:20 dpdklab
2023-03-18  1:01 dpdklab
2023-03-18  0:49 dpdklab
2023-03-18  0:48 dpdklab
2023-03-18  0:48 dpdklab
2023-03-18  0:42 dpdklab
2023-03-18  0:34 dpdklab
2023-03-18  0:31 dpdklab
2023-03-18  0:30 dpdklab
2023-03-18  0:30 dpdklab
2023-03-18  0:28 dpdklab
2023-03-18  0:27 dpdklab
2023-03-18  0:24 dpdklab
2023-03-18  0:21 dpdklab
2023-03-18  0:18 dpdklab
2023-03-18  0:18 dpdklab
2023-03-18  0:15 dpdklab
2023-03-18  0:13 dpdklab
2023-03-18  0:09 dpdklab
2023-03-18  0:03 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=202303172321.32HNLWfI1664873@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).