automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135264 [PATCH] drivers: use dedicated logtypes
Date: Mon, 18 Dec 2023 21:40:58 +0800	[thread overview]
Message-ID: <202312181340.3BIDewwX2421236@localhost.localdomain> (raw)
In-Reply-To: <20231218135932.1497163-1-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 18 Dec 2023 14:59:31 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135264 --> 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-12-18 14:02 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231218135932.1497163-1-david.marchand@redhat.com>
2023-12-18 13:40 ` qemudev [this message]
2023-12-18 13:45 ` qemudev
2023-12-18 14:00 ` checkpatch
2023-12-18 15:04 ` 0-day Robot
2023-12-18 14:48 dpdklab
2023-12-18 14:48 dpdklab
2023-12-18 14:49 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:52 dpdklab
2023-12-18 14:53 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:58 dpdklab
2023-12-18 14:58 dpdklab
2023-12-18 15:00 dpdklab
2023-12-18 15:00 dpdklab
2023-12-18 15:01 dpdklab
2023-12-18 15:02 dpdklab
2023-12-18 15:03 dpdklab
2023-12-18 15:03 dpdklab
2023-12-18 15:04 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:06 dpdklab
2023-12-18 15:06 dpdklab
2023-12-18 15:06 dpdklab
2023-12-18 15:08 dpdklab
2023-12-18 15:08 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:10 dpdklab
2023-12-18 15:10 dpdklab
2023-12-18 15:12 dpdklab
2023-12-18 15:13 dpdklab
2023-12-18 15:14 dpdklab
2023-12-18 15:16 dpdklab
2023-12-18 15:16 dpdklab
2023-12-18 15:18 dpdklab
2023-12-18 15:18 dpdklab
2023-12-18 15:19 dpdklab
2023-12-18 15:19 dpdklab
2023-12-18 15:20 dpdklab
2023-12-18 15:22 dpdklab
2023-12-18 15:24 dpdklab
2023-12-18 15:24 dpdklab
2023-12-18 15:27 dpdklab
2023-12-18 15:28 dpdklab
2023-12-18 15:28 dpdklab
2023-12-18 15:31 dpdklab
2023-12-18 15:32 dpdklab
2023-12-18 15:33 dpdklab
2023-12-18 15:39 dpdklab
2023-12-18 16:12 dpdklab
2023-12-18 18:07 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=202312181340.3BIDewwX2421236@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).