automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139559 [PATCH] net/ionic: clean up logging issues
Date: Mon, 22 Apr 2024 10:00:31 +0800	[thread overview]
Message-ID: <202404220200.43M20VNJ189790@localhost.localdomain> (raw)
In-Reply-To: <20240419202556.46188-1-andrew.boyer@amd.com>

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

_Compilation OK_

Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Fri, 19 Apr 2024 13:25:56 -0700
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 7b668b7d65ba33783c280d08489fa31685bd0ee6

139559 --> 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:[~2024-04-22  2:28 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240419202556.46188-1-andrew.boyer@amd.com>
2024-04-19 20:27 ` checkpatch
2024-04-20  0:33 ` dpdklab
2024-04-20  0:34 ` dpdklab
2024-04-20  0:34 ` dpdklab
2024-04-20  0:34 ` dpdklab
2024-04-20  0:35 ` dpdklab
2024-04-20  0:52 ` dpdklab
2024-04-20  1:01 ` dpdklab
2024-04-20  1:03 ` dpdklab
2024-04-20  1:03 ` dpdklab
2024-04-20  1:04 ` dpdklab
2024-04-20  1:04 ` dpdklab
2024-04-20  1:04 ` dpdklab
2024-04-20  1:05 ` dpdklab
2024-04-20  1:05 ` dpdklab
2024-04-20  1:05 ` dpdklab
2024-04-20  1:05 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:06 ` dpdklab
2024-04-20  1:07 ` dpdklab
2024-04-20  1:08 ` dpdklab
2024-04-20  1:08 ` dpdklab
2024-04-20  1:08 ` dpdklab
2024-04-20  1:08 ` dpdklab
2024-04-20  1:09 ` dpdklab
2024-04-20  1:09 ` dpdklab
2024-04-20  1:09 ` dpdklab
2024-04-20  1:09 ` dpdklab
2024-04-20  1:10 ` dpdklab
2024-04-20  1:10 ` dpdklab
2024-04-20  1:10 ` dpdklab
2024-04-20  1:11 ` dpdklab
2024-04-20  1:11 ` dpdklab
2024-04-20  1:11 ` dpdklab
2024-04-20  1:11 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:12 ` dpdklab
2024-04-20  1:13 ` dpdklab
2024-04-20  1:13 ` dpdklab
2024-04-20  1:13 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:20 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:21 ` dpdklab
2024-04-20  1:22 ` dpdklab
2024-04-20  1:22 ` dpdklab
2024-04-20  1:22 ` dpdklab
2024-04-20  1:31 ` dpdklab
2024-04-20  1:31 ` dpdklab
2024-04-20  1:32 ` dpdklab
2024-04-20  1:32 ` dpdklab
2024-04-20  1:33 ` dpdklab
2024-04-20  1:33 ` dpdklab
2024-04-20  1:33 ` dpdklab
2024-04-20  1:34 ` dpdklab
2024-04-20  1:35 ` dpdklab
2024-04-20  1:35 ` dpdklab
2024-04-20  1:36 ` dpdklab
2024-04-20  1:41 ` dpdklab
2024-04-20  1:47 ` dpdklab
2024-04-20  1:51 ` dpdklab
2024-04-20  1:52 ` dpdklab
2024-04-20  2:12 ` dpdklab
2024-04-20  2:12 ` dpdklab
2024-04-20  2:26 ` dpdklab
2024-04-20  2:31 ` dpdklab
2024-04-22  2:00 ` qemudev [this message]
2024-04-22  2:05 ` qemudev

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=202404220200.43M20VNJ189790@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).