automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128386 [PATCH] config/arm: fix Neoverse N2 march flag
Date: Thu, 8 Jun 2023 15:16:41 +0800	[thread overview]
Message-ID: <202306080716.3587GfdF1891305@localhost.localdomain> (raw)
In-Reply-To: <20230608072757.9513-1-pbhagavatula@marvell.com>

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

_Compilation OK_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thu, 8 Jun 2023 12:57:57 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 55ead98d1de1b02fa563e822a67c7adc0361ddfb

128386 --> 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-06-08  7:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230608072757.9513-1-pbhagavatula@marvell.com>
2023-06-08  7:16 ` qemudev [this message]
2023-06-08  7:20 ` qemudev
2023-06-08  7:28 ` checkpatch
2023-06-08 10:19 ` 0-day Robot
2023-06-08 16:09 dpdklab
2023-06-08 16:10 dpdklab
2023-06-08 16:18 dpdklab
2023-06-08 16:21 dpdklab
2023-06-08 16:34 dpdklab
2023-06-08 16:34 dpdklab
2023-06-08 16:55 dpdklab
2023-06-08 17:07 dpdklab
2023-06-08 19:59 dpdklab
2023-06-08 20:00 dpdklab
2023-06-08 20:04 dpdklab
2023-06-08 22:50 dpdklab
2023-06-08 23:01 dpdklab
2023-06-09  0:52 dpdklab
2023-06-09  0:56 dpdklab
2023-06-09  1:37 dpdklab
2023-06-09  1:40 dpdklab
2023-06-09  1:50 dpdklab
2023-06-09 16:48 dpdklab
2023-06-09 21:10 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=202306080716.3587GfdF1891305@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).