automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139247-139248 [PATCH 2/2] doc/prog_guide: document direct link bonding mode
Date: Fri, 12 Apr 2024 19:57:14 +0800	[thread overview]
Message-ID: <202404121157.43CBvDbt2772163@localhost.localdomain> (raw)
In-Reply-To: <20240412122006.101673-2-vojanec@cesnet.cz>

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

_Compilation OK_

Submitter: Kamil Vojanec <vojanec@cesnet.cz>
Date: Fri, 12 Apr 2024 14:20:05 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 6db5f91b5e628671c341b833f21ea35e65e9699d

139247-139248 --> 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:[~2024-04-12 12:22 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240412122006.101673-2-vojanec@cesnet.cz>
2024-04-12 11:57 ` qemudev [this message]
2024-04-12 12:01 ` qemudev
2024-04-12 12:22 ` |WARNING| pw139248 " checkpatch
2024-04-12 13:24 ` |SUCCESS| " 0-day Robot
2024-04-13  0:57 ` |SUCCESS| pw139247-139248 [PATCH] [2/2] doc/prog_guide: document dir dpdklab
2024-04-13  1:12 ` dpdklab
2024-04-13  1:13 ` dpdklab
2024-04-13  1:13 ` dpdklab
2024-04-13  1:14 ` dpdklab
2024-04-13  1:15 ` dpdklab
2024-04-13  1:15 ` dpdklab
2024-04-13  1:22 ` dpdklab
2024-04-13  1:23 ` dpdklab
2024-04-13  1:23 ` dpdklab
2024-04-13  1:23 ` dpdklab
2024-04-13  1:24 ` dpdklab
2024-04-13  1:25 ` dpdklab
2024-04-13  1:27 ` dpdklab
2024-04-13  1:27 ` dpdklab
2024-04-13  1:41 ` dpdklab
2024-04-13  1:45 ` dpdklab
2024-04-13  1:49 ` dpdklab
2024-04-13  2:26 ` dpdklab
2024-04-13  2:27 ` dpdklab
2024-04-13  2:27 ` dpdklab
2024-04-13  2:29 ` dpdklab
2024-04-13  2:29 ` dpdklab
2024-04-13  2:31 ` dpdklab
2024-04-13  2:31 ` dpdklab
2024-04-13  2:35 ` dpdklab
2024-04-13  2:38 ` dpdklab
2024-04-13  2:45 ` dpdklab
2024-04-13  2:46 ` dpdklab
2024-04-13  2:46 ` dpdklab
2024-04-13  2:46 ` dpdklab
2024-04-13  2:47 ` dpdklab
2024-04-13  2:48 ` dpdklab
2024-04-13  2:48 ` dpdklab
2024-04-13  2:49 ` dpdklab
2024-04-13  2:49 ` dpdklab
2024-04-13  2:50 ` dpdklab
2024-04-13  2:51 ` dpdklab
2024-04-13  2:52 ` dpdklab
2024-04-13  2:52 ` dpdklab
2024-04-13  2:53 ` dpdklab
2024-04-13  2:53 ` dpdklab
2024-04-13  2:53 ` dpdklab
2024-04-13  2:54 ` dpdklab
2024-04-13  2:54 ` dpdklab
2024-04-13  2:54 ` dpdklab
2024-04-13  2:55 ` dpdklab
2024-04-13  2:57 ` dpdklab
2024-04-13  2:57 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:58 ` dpdklab
2024-04-13  2:59 ` dpdklab
2024-04-13  3:00 ` dpdklab
2024-04-13  3:01 ` dpdklab
2024-04-13  3:02 ` dpdklab
2024-04-13  3:02 ` dpdklab
2024-04-13  3:02 ` dpdklab
2024-04-13  3:03 ` dpdklab
2024-04-13  3:04 ` dpdklab
2024-04-13  3:04 ` dpdklab
2024-04-13  3:04 ` dpdklab
2024-04-13  3:05 ` dpdklab
2024-04-13  3:06 ` dpdklab
2024-04-13  3:07 ` dpdklab
2024-04-13  3:07 ` dpdklab
2024-04-13  3:07 ` dpdklab
2024-04-13  3:07 ` dpdklab
2024-04-13  3:09 ` dpdklab
2024-04-13  3:09 ` dpdklab
2024-04-13  3:09 ` dpdklab
2024-04-13  3:24 ` dpdklab
2024-04-13  3:37 ` dpdklab
2024-04-13  3:38 ` dpdklab
2024-04-13  3:43 ` dpdklab
2024-04-13  3:44 ` dpdklab
2024-04-13  3:46 ` dpdklab
2024-04-13  3:47 ` dpdklab
2024-04-13  3:51 ` dpdklab
2024-04-13  3:55 ` dpdklab
2024-04-13  5:20 ` dpdklab
2024-04-13  5:42 ` 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=202404121157.43CBvDbt2772163@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).