automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121685 [PATCH] kni: fix build on RHEL 9.1
Date: Sat, 7 Jan 2023 04:05:39 +0800	[thread overview]
Message-ID: <202301062005.306K5dU3274453@localhost.localdomain> (raw)
In-Reply-To: <20230106201315.1179306-1-ferruh.yigit@amd.com>

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

_Compilation OK_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Fri, 6 Jan 2023 20:13:14 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 7f822ec8cb38a794e8d406fc59e7e4612c4695db

121685 --> 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-01-06 20:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230106201315.1179306-1-ferruh.yigit@amd.com>
2023-01-06 20:05 ` qemudev [this message]
2023-01-06 20:09 ` qemudev
2023-01-06 20:14 ` checkpatch
2023-01-06 20:59 ` 0-day Robot
2023-01-06 20:40 dpdklab
2023-01-06 20:40 dpdklab
2023-01-06 20:45 dpdklab
2023-01-06 20:46 dpdklab
2023-01-06 20:49 dpdklab
2023-01-06 20:56 dpdklab
2023-01-06 21:00 dpdklab
2023-01-06 21:23 dpdklab
2023-01-06 21:53 dpdklab
2023-01-06 21:53 dpdklab
2023-01-06 22:00 dpdklab
2023-01-06 22:04 dpdklab
2023-01-06 22:05 dpdklab
2023-01-06 22:07 dpdklab
2023-01-06 22:09 dpdklab
2023-01-06 22:10 dpdklab
2023-01-06 22:20 dpdklab
2023-01-06 22:24 dpdklab
2023-01-06 22:59 dpdklab
2023-01-06 23:29 dpdklab
2023-01-06 23:34 dpdklab
2023-01-06 23:35 dpdklab
2023-01-06 23:35 dpdklab
2023-01-06 23:35 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=202301062005.306K5dU3274453@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).