automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137488-137489 [v10 3/3] net/af_xdp: support AF_XDP DP pinned maps
Date: Thu, 29 Feb 2024 20:40:40 +0800	[thread overview]
Message-ID: <202402291240.41TCee6Y2110391@localhost.localdomain> (raw)
In-Reply-To: <20240229130212.343036-4-mtahhan@redhat.com>

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

_Compilation OK_

Submitter: Maryam Tahhan <mtahhan@redhat.com>
Date: Thu, 29 Feb 2024 08:01:22 -0500
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: f60df26faa3c90fc66d356e16347acd046971441

137488-137489 --> 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-02-29 13:05 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229130212.343036-4-mtahhan@redhat.com>
2024-02-29 12:40 ` qemudev [this message]
2024-02-29 12:45 ` qemudev
2024-02-29 13:04 ` |SUCCESS| pw137489 " checkpatch
2024-02-29 14:05 ` 0-day Robot
2024-02-29 16:00 ` |SUCCESS| pw137488-137489 [PATCH] [v10,3/3] net/af_xdp: support AF_X dpdklab
2024-02-29 16:09 ` dpdklab
2024-02-29 16:10 ` dpdklab
2024-02-29 16:17 ` dpdklab
2024-02-29 16:23 ` dpdklab
2024-02-29 16:25 ` dpdklab
2024-02-29 16:28 ` dpdklab
2024-02-29 16:29 ` dpdklab
2024-02-29 16:35 ` dpdklab
2024-02-29 16:36 ` dpdklab
2024-02-29 16:37 ` dpdklab
2024-02-29 16:37 ` dpdklab
2024-02-29 16:40 ` dpdklab
2024-02-29 16:41 ` dpdklab
2024-02-29 16:42 ` dpdklab
2024-02-29 16:43 ` dpdklab
2024-02-29 17:55 ` dpdklab
2024-02-29 18:27 ` dpdklab
2024-02-29 18:28 ` dpdklab
2024-02-29 18:28 ` dpdklab
2024-02-29 18:29 ` dpdklab
2024-02-29 18:32 ` dpdklab
2024-02-29 18:42 ` dpdklab
2024-02-29 18:42 ` dpdklab
2024-02-29 18:42 ` dpdklab
2024-02-29 18:44 ` dpdklab
2024-02-29 18:47 ` dpdklab
2024-02-29 18:58 ` dpdklab
2024-02-29 18:58 ` dpdklab
2024-02-29 18:59 ` dpdklab
2024-02-29 19:05 ` dpdklab
2024-02-29 19:05 ` dpdklab
2024-02-29 19:05 ` dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:07 ` dpdklab
2024-02-29 19:07 ` dpdklab
2024-02-29 19:08 ` dpdklab
2024-02-29 19:09 ` dpdklab
2024-02-29 19:09 ` dpdklab
2024-02-29 19:10 ` dpdklab
2024-02-29 19:10 ` dpdklab
2024-02-29 19:10 ` dpdklab
2024-02-29 19:15 ` dpdklab
2024-02-29 19:15 ` dpdklab
2024-02-29 19:16 ` dpdklab
2024-02-29 19:16 ` dpdklab
2024-02-29 19:16 ` dpdklab
2024-02-29 19:16 ` dpdklab
2024-02-29 19:17 ` dpdklab
2024-02-29 19:17 ` dpdklab
2024-02-29 19:17 ` dpdklab
2024-02-29 19:18 ` dpdklab
2024-02-29 19:18 ` dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:21 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:49 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-02-29 20:09 ` dpdklab
2024-03-01  1:51 ` dpdklab
2024-03-01  8:06 ` dpdklab
2024-03-01  8:11 ` dpdklab
2024-03-01  8:16 ` dpdklab
2024-03-01  8:21 ` dpdklab
2024-03-02  8:06 ` dpdklab
2024-03-03  7:59 ` dpdklab
2024-03-03  8:31 ` dpdklab
2024-03-03  9:04 ` 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=202402291240.41TCee6Y2110391@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).