automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120708-120714 [PATCH V2 11/11] ethdev: display capability values in hexadecimal format
Date: Sat, 10 Dec 2022 08:13:41 +0800	[thread overview]
Message-ID: <202212100013.2BA0Df6i1018641@localhost.localdomain> (raw)
In-Reply-To: <20221209110450.62456-12-lihuisong@huawei.com>

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

_Compilation OK_

Submitter: Huisong Li <lihuisong@huawei.com>
Date: Fri, 9 Dec 2022 19:04:40 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c581c49cd3fcaff596fbe566e270b442e6326c79

120708-120714 --> 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


  parent reply	other threads:[~2022-12-10  0:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221209110450.62456-12-lihuisong@huawei.com>
2022-12-09 11:07 ` |SUCCESS| pw120714 " checkpatch
2022-12-09 12:38 ` 0-day Robot
2022-12-10  0:13 ` qemudev [this message]
2022-12-10  0:14 ` |SUCCESS| pw120708-120714 " qemudev
2022-12-09 11:29 |SUCCESS| pw120708-120714 [PATCH] [V2, " dpdklab
2022-12-09 11:33 dpdklab
2022-12-09 11:36 dpdklab
2022-12-09 11:38 dpdklab
2022-12-09 11:45 dpdklab
2022-12-09 11:50 dpdklab
2022-12-09 11:53 dpdklab
2022-12-09 11:53 dpdklab
2022-12-09 12:04 dpdklab
2022-12-09 12:09 dpdklab
2022-12-09 12:10 dpdklab
2022-12-09 12:17 dpdklab
2022-12-09 12:19 dpdklab
2022-12-09 12:28 dpdklab
2022-12-09 12:30 dpdklab
2022-12-09 12:31 dpdklab
2022-12-09 12:32 dpdklab
2022-12-09 12:50 dpdklab
2022-12-09 12:52 dpdklab
2022-12-09 12:54 dpdklab
2022-12-09 12:55 dpdklab
2022-12-09 12:55 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=202212100013.2BA0Df6i1018641@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).