automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137491-137493 [v11 3/3] net/af_xdp: support AF_XDP DP pinned maps
Date: Thu, 29 Feb 2024 21:00:00 +0800	[thread overview]
Message-ID: <202402291300.41TD00nV2165035@localhost.localdomain> (raw)
In-Reply-To: <20240229132129.656166-4-mtahhan@redhat.com>

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

_Compilation OK_

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

137491-137493 --> 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:24 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229132129.656166-4-mtahhan@redhat.com>
2024-02-29 13:00 ` qemudev [this message]
2024-02-29 13:04 ` qemudev
2024-02-29 13:22 ` |SUCCESS| pw137493 " checkpatch
2024-02-29 14:25 ` 0-day Robot
2024-02-29 15:41 ` |SUCCESS| pw137491-137493 [PATCH] [v11,3/3] net/af_xdp: support AF_X dpdklab
2024-02-29 15:43 ` dpdklab
2024-02-29 15:46 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 15:59 ` dpdklab
2024-02-29 16:06 ` dpdklab
2024-02-29 16:15 ` dpdklab
2024-02-29 16:30 ` dpdklab
2024-02-29 16:34 ` dpdklab
2024-02-29 16:34 ` dpdklab
2024-02-29 16:34 ` 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:37 ` dpdklab
2024-02-29 16:38 ` dpdklab
2024-02-29 17:39 ` dpdklab
2024-02-29 17:40 ` dpdklab
2024-02-29 17:40 ` dpdklab
2024-02-29 17:46 ` dpdklab
2024-02-29 17:49 ` dpdklab
2024-02-29 17:55 ` dpdklab
2024-02-29 17:55 ` dpdklab
2024-02-29 17:55 ` dpdklab
2024-02-29 17:56 ` dpdklab
2024-02-29 17:56 ` dpdklab
2024-02-29 17:57 ` dpdklab
2024-02-29 17:57 ` dpdklab
2024-02-29 17:57 ` dpdklab
2024-02-29 18:02 ` dpdklab
2024-02-29 18:02 ` dpdklab
2024-02-29 18:03 ` dpdklab
2024-02-29 18:03 ` dpdklab
2024-02-29 18:04 ` dpdklab
2024-02-29 18:05 ` dpdklab
2024-02-29 18:05 ` dpdklab
2024-02-29 18:06 ` dpdklab
2024-02-29 18:07 ` dpdklab
2024-02-29 18:10 ` dpdklab
2024-02-29 18:10 ` dpdklab
2024-02-29 18:12 ` dpdklab
2024-02-29 18:12 ` dpdklab
2024-02-29 18:13 ` dpdklab
2024-02-29 18:13 ` dpdklab
2024-02-29 18:14 ` dpdklab
2024-02-29 18:14 ` dpdklab
2024-02-29 18:15 ` dpdklab
2024-02-29 18:16 ` dpdklab
2024-02-29 18:17 ` dpdklab
2024-02-29 18:17 ` dpdklab
2024-02-29 18:18 ` dpdklab
2024-02-29 18:18 ` dpdklab
2024-02-29 18:20 ` dpdklab
2024-02-29 18:20 ` dpdklab
2024-02-29 18:25 ` dpdklab
2024-02-29 18:26 ` dpdklab
2024-02-29 18:26 ` dpdklab
2024-02-29 18:29 ` dpdklab
2024-02-29 18:36 ` dpdklab
2024-02-29 18:43 ` dpdklab
2024-02-29 19:49 ` dpdklab
2024-03-01  0:35 ` dpdklab
2024-03-01  7:44 ` dpdklab
2024-03-01  7:49 ` dpdklab
2024-03-01  7:53 ` dpdklab
2024-03-01  7:59 ` dpdklab
2024-03-02  7:34 ` dpdklab
2024-03-03  6:20 ` dpdklab
2024-03-03  6:53 ` dpdklab
2024-03-03  7:28 ` 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=202402291300.41TD00nV2165035@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).