automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132016-132017 [PATCH v5 2/2] node: add UDP v4 support
Date: Wed, 27 Sep 2023 20:27:47 +0800	[thread overview]
Message-ID: <202309271227.38RCRlKa3197757@localhost.localdomain> (raw)
In-Reply-To: <20230927124100.4108588-2-rkudurumalla@marvell.com>

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

_Compilation OK_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wed, 27 Sep 2023 18:10:59 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 39970abcf4850e070aa4709c87bcac15cb27caf8

132016-132017 --> 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-09-27 12:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230927124100.4108588-2-rkudurumalla@marvell.com>
2023-09-27 12:27 ` qemudev [this message]
2023-09-27 12:32 ` qemudev
2023-09-27 12:41 ` |WARNING| pw132017 " checkpatch
2023-09-27 13:39 ` |SUCCESS| " 0-day Robot
2023-09-27 15:53 |SUCCESS| pw132016-132017 [PATCH] [v5,2/2] " dpdklab
2023-09-27 15:53 dpdklab
2023-09-27 15:54 dpdklab
2023-09-27 15:54 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 16:00 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:06 dpdklab
2023-09-27 16:06 dpdklab
2023-09-27 16:12 dpdklab
2023-09-27 16:25 dpdklab
2023-09-27 16:25 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:27 dpdklab
2023-09-27 16:28 dpdklab
2023-09-27 16:28 dpdklab
2023-09-27 16:29 dpdklab
2023-09-27 16:30 dpdklab
2023-09-27 16:31 dpdklab
2023-09-27 16:31 dpdklab
2023-09-27 16:32 dpdklab
2023-09-27 16:44 dpdklab
2023-09-27 16:45 dpdklab
2023-09-27 16:46 dpdklab
2023-09-27 16:47 dpdklab
2023-09-27 17:13 dpdklab
2023-09-27 20:58 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=202309271227.38RCRlKa3197757@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).