automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123405-123406 [PATCH v2 2/2] baseband/acc: add check for empty queue
Date: Wed, 8 Feb 2023 09:49:30 +0800	[thread overview]
Message-ID: <202302080149.3181nUDY1459026@localhost.localdomain> (raw)
In-Reply-To: <20230208020001.181055-3-hernan.vargas@intel.com>

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

_Compilation OK_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Tue,  7 Feb 2023 18:00:00 -0800
DPDK git baseline: Repo:dpdk-next-baseband
  Branch: for-main
  CommitID: 341c7568f2ed33cab936f8e60de8ab25bf50f0ea

123405-123406 --> 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  2:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230208020001.181055-3-hernan.vargas@intel.com>
2023-02-08  1:49 ` qemudev [this message]
2023-02-08  1:53 ` qemudev
2023-02-08  2:01 ` |SUCCESS| pw123406 " checkpatch
2023-02-08  2:59 ` 0-day Robot
2023-02-14  6:10 |SUCCESS| pw123405-123406 [PATCH] [v2, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-12 14:31 dpdklab
2023-02-12 14:31 dpdklab
2023-02-12 14:29 dpdklab
2023-02-12 14:28 dpdklab
2023-02-12 14:27 dpdklab
2023-02-12 14:26 dpdklab
2023-02-12 14:21 dpdklab
2023-02-12 14:20 dpdklab
2023-02-12 14:18 dpdklab
2023-02-12 14:14 dpdklab
2023-02-12 14:08 dpdklab
2023-02-12 14:03 dpdklab
2023-02-12 13:55 dpdklab
2023-02-12 13:41 dpdklab
2023-02-10 13:41 dpdklab
2023-02-10  4:46 dpdklab
2023-02-09 16:25 dpdklab
2023-02-09  4:48 dpdklab
2023-02-09  4:48 dpdklab
2023-02-09  4:47 dpdklab
2023-02-09  4:47 dpdklab
2023-02-09  4:47 dpdklab
2023-02-09  4:47 dpdklab
2023-02-09  4:46 dpdklab
2023-02-09  4:46 dpdklab
2023-02-09  4:45 dpdklab
2023-02-09  3:31 dpdklab
2023-02-08 17:45 dpdklab
2023-02-08  4:05 dpdklab
2023-02-08  2:50 dpdklab
2023-02-08  2:47 dpdklab
2023-02-08  2:44 dpdklab
2023-02-08  2:43 dpdklab
2023-02-08  2:40 dpdklab
2023-02-08  2:38 dpdklab
2023-02-08  2:37 dpdklab
2023-02-08  2:36 dpdklab
2023-02-08  2:30 dpdklab
2023-02-08  2:27 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=202302080149.3181nUDY1459026@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).