automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121746-121747 [PATCH v4 2/2] eal: provide leading and trailing zero bit count abstraction
Date: Tue, 10 Jan 2023 01:29:02 +0800	[thread overview]
Message-ID: <202301091729.309HT2Is1569414@localhost.localdomain> (raw)
In-Reply-To: <1673285784-14394-3-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon,  9 Jan 2023 09:36:23 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 373f4c7de8ff350548cacc3d56e788461677f2c7

121746-121747 --> 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-01-09 17:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1673285784-14394-3-git-send-email-roretzla@linux.microsoft.com>
2023-01-09 17:29 ` qemudev [this message]
2023-01-09 17:32 ` qemudev
2023-01-09 17:36 ` |WARNING| pw121747 " checkpatch
2023-01-09 20:00 ` |SUCCESS| " 0-day Robot
2023-01-09 18:00 |SUCCESS| pw121746-121747 [PATCH] [v4, " dpdklab
2023-01-09 18:01 dpdklab
2023-01-09 18:01 dpdklab
2023-01-09 18:05 dpdklab
2023-01-09 18:06 dpdklab
2023-01-09 18:16 dpdklab
2023-01-09 18:20 dpdklab
2023-01-09 20:06 dpdklab
2023-01-09 20:19 dpdklab
2023-01-09 20:47 dpdklab
2023-01-09 20:51 dpdklab
2023-01-09 21:07 dpdklab
2023-01-09 21:07 dpdklab
2023-01-09 21:07 dpdklab
2023-01-09 21:08 dpdklab
2023-01-09 21:09 dpdklab
2023-01-09 21:26 dpdklab
2023-01-09 21:27 dpdklab
2023-01-10  1:28 dpdklab
2023-01-10  1:47 dpdklab
2023-01-10  2:45 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=202301091729.309HT2Is1569414@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).