automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130049 [PATCH] net/bonding: Fix header for C++
Date: Wed, 9 Aug 2023 23:41:31 +0800	[thread overview]
Message-ID: <202308091541.379FfVxD1343248@localhost.localdomain> (raw)
In-Reply-To: <hxLTO3XMJ2hUmnvx@hankala.org>

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

_Compilation OK_

Submitter: Visa Hankala <visa@hankala.org>
Date: Wed, 9 Aug 2023 15:52:41 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 0ae35eceb9e4569b0814fcf671b4455301bb7518

130049 --> 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-08-09 15:55 UTC|newest]

Thread overview: 101+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hxLTO3XMJ2hUmnvx@hankala.org>
2023-08-09 15:41 ` qemudev [this message]
2023-08-09 15:46 ` qemudev
2023-08-09 15:54 ` checkpatch
2023-08-09 16:39 ` 0-day Robot
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:29 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:30 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:31 dpdklab
2023-08-10 14:36 dpdklab
2023-08-10 14:38 dpdklab
2023-08-10 14:56 dpdklab
2023-08-10 14:57 dpdklab
2023-08-10 15:06 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:13 dpdklab
2023-08-10 15:16 dpdklab
2023-08-10 15:30 dpdklab
2023-08-10 15:54 dpdklab
2023-08-10 16:11 dpdklab
2023-08-11  2:01 dpdklab
2023-08-11  2:20 dpdklab
2023-08-11  2:24 dpdklab
2023-08-11  2:26 dpdklab
2023-08-11  2:29 dpdklab
2023-08-11  2:39 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:40 dpdklab
2023-08-11  2:41 dpdklab
2023-08-11  2:41 dpdklab
2023-08-11  2:42 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:45 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:46 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:47 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:48 dpdklab
2023-08-11  2:52 dpdklab
2023-08-11  2:59 dpdklab
2023-08-11  3:47 dpdklab
2023-08-11  3:56 dpdklab
2023-08-11  3:57 dpdklab
2023-08-11  3:58 dpdklab
2023-08-11  4:10 dpdklab
2023-08-11  4:12 dpdklab
2023-08-11  4:15 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:20 dpdklab
2023-08-11  4:22 dpdklab
2023-08-11  4:25 dpdklab
2023-08-11  4:28 dpdklab
2023-08-11  4:30 dpdklab
2023-08-11  4:31 dpdklab
2023-08-11  4:33 dpdklab
2023-08-11  4:34 dpdklab
2023-08-11  4:34 dpdklab
2023-08-11  4:35 dpdklab
2023-08-11  8:10 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:06 dpdklab
2023-08-11 20:09 dpdklab
2023-08-11 20:09 dpdklab
2023-08-11 20:11 dpdklab
2023-08-11 20:12 dpdklab
2023-08-11 20:13 dpdklab
2023-08-11 20:15 dpdklab
2023-08-11 21:35 dpdklab
2023-08-13 19:14 dpdklab
2023-08-13 21:57 dpdklab
2023-08-14  1:34 dpdklab
2023-08-14  1:35 dpdklab
2023-08-14  1:38 dpdklab
2023-08-14  1:39 dpdklab
2023-08-14  1:40 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:41 dpdklab
2023-08-14  1:42 dpdklab
2023-08-14  1:45 dpdklab
2023-08-14  1:54 dpdklab
2023-08-14  1:57 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=202308091541.379FfVxD1343248@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).