automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133158 [PATCH v2] maintainers: update email address
Date: Mon, 23 Oct 2023 12:55:03 +0800	[thread overview]
Message-ID: <202310230455.39N4t33q1202841@localhost.localdomain> (raw)
In-Reply-To: <20231023051324.74585-1-chenbox@nvidia.com>

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

_Compilation OK_

Submitter: Chenbo Xia <chenbox@nvidia.com>
Date: Mon, 23 Oct 2023 13:13:24 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2cd2cf0cc53a508c4bd951a980ec534a646260de

133158 --> 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-10-23  5:16 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231023051324.74585-1-chenbox@nvidia.com>
2023-10-23  4:55 ` qemudev [this message]
2023-10-23  4:59 ` qemudev
2023-10-23  5:14 ` checkpatch
2023-10-23  6:19 ` 0-day Robot
2023-10-23  9:18 |SUCCESS| pw133158 [PATCH] [v2] " dpdklab
2023-10-23  9:18 dpdklab
2023-10-23  9:24 dpdklab
2023-10-23  9:24 dpdklab
2023-10-23  9:45 dpdklab
2023-10-23  9:47 dpdklab
2023-10-23  9:48 dpdklab
2023-10-23  9:48 dpdklab
2023-10-23  9:48 dpdklab
2023-10-23  9:49 dpdklab
2023-10-23  9:49 dpdklab
2023-10-23  9:49 dpdklab
2023-10-23  9:49 dpdklab
2023-10-23  9:50 dpdklab
2023-10-23  9:50 dpdklab
2023-10-23  9:50 dpdklab
2023-10-23  9:50 dpdklab
2023-10-23  9:51 dpdklab
2023-10-23  9:51 dpdklab
2023-10-23  9:51 dpdklab
2023-10-23  9:52 dpdklab
2023-10-23  9:52 dpdklab
2023-10-23  9:52 dpdklab
2023-10-23  9:53 dpdklab
2023-10-23  9:53 dpdklab
2023-10-23  9:53 dpdklab
2023-10-23  9:53 dpdklab
2023-10-23  9:54 dpdklab
2023-10-23  9:54 dpdklab
2023-10-23  9:58 dpdklab
2023-10-23  9:59 dpdklab
2023-10-23 10:00 dpdklab
2023-10-23 10:08 dpdklab
2023-10-23 10:09 dpdklab
2023-10-23 10:09 dpdklab
2023-10-23 10:16 dpdklab
2023-10-23 10:17 dpdklab
2023-10-23 10:17 dpdklab
2023-10-23 10:17 dpdklab
2023-10-23 10:18 dpdklab
2023-10-23 10:18 dpdklab
2023-10-23 10:19 dpdklab
2023-10-23 10:19 dpdklab
2023-10-23 10:19 dpdklab
2023-10-23 10:20 dpdklab
2023-10-23 10:20 dpdklab
2023-10-23 10:20 dpdklab
2023-10-23 10:21 dpdklab
2023-10-23 10:21 dpdklab
2023-10-23 10:22 dpdklab
2023-10-23 10:39 dpdklab
2023-10-23 10:41 dpdklab
2023-10-23 11:31 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=202310230455.39N4t33q1202841@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).