automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133629 [PATCH] config/arm: add cortex-A55 part number
Date: Mon, 30 Oct 2023 23:36:07 +0800	[thread overview]
Message-ID: <202310301536.39UFa7wg3302440@localhost.localdomain> (raw)
In-Reply-To: <20231030155151.4101420-1-hemant.agrawal@nxp.com>

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

_Compilation OK_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Mon, 30 Oct 2023 21:21:51 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 32faaf30732cb4006cd1e45997403427029ef5fe

133629 --> 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-30 15:57 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231030155151.4101420-1-hemant.agrawal@nxp.com>
2023-10-30 15:36 ` qemudev [this message]
2023-10-30 15:40 ` qemudev
2023-10-30 15:53 ` checkpatch
2023-10-30 17:35 ` 0-day Robot
2023-10-30 16:40 dpdklab
2023-10-30 16:43 dpdklab
2023-10-30 16:43 dpdklab
2023-10-30 16:52 dpdklab
2023-10-30 16:52 dpdklab
2023-10-30 16:53 dpdklab
2023-10-30 16:53 dpdklab
2023-10-30 16:54 dpdklab
2023-10-30 16:54 dpdklab
2023-10-30 16:54 dpdklab
2023-10-30 16:54 dpdklab
2023-10-30 16:54 dpdklab
2023-10-30 16:55 dpdklab
2023-10-30 16:55 dpdklab
2023-10-30 16:55 dpdklab
2023-10-30 16:56 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:57 dpdklab
2023-10-30 16:58 dpdklab
2023-10-30 16:58 dpdklab
2023-10-30 16:58 dpdklab
2023-10-30 16:59 dpdklab
2023-10-30 16:59 dpdklab
2023-10-30 16:59 dpdklab
2023-10-30 16:59 dpdklab
2023-10-30 16:59 dpdklab
2023-10-30 17:00 dpdklab
2023-10-30 17:00 dpdklab
2023-10-30 17:00 dpdklab
2023-10-30 17:00 dpdklab
2023-10-30 17:02 dpdklab
2023-10-30 17:04 dpdklab
2023-10-30 17:06 dpdklab
2023-10-30 17:10 dpdklab
2023-10-30 17:12 dpdklab
2023-10-30 17:13 dpdklab
2023-10-30 17:14 dpdklab
2023-10-30 17:14 dpdklab
2023-10-30 17:16 dpdklab
2023-10-30 17:17 dpdklab
2023-10-30 17:24 dpdklab
2023-10-30 17:25 dpdklab
2023-10-30 17:25 dpdklab
2023-10-30 17:28 dpdklab
2023-10-30 17:45 dpdklab
2023-10-30 17:48 dpdklab
2023-10-30 17:54 dpdklab
2023-10-30 18:21 dpdklab
2023-10-30 18:22 dpdklab
2023-10-30 18:23 dpdklab
2023-10-31  0: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=202310301536.39UFa7wg3302440@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).