automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139097-139099 [v13 3/3] net/af_xdp: support AF_XDP DP pinned maps
Date: Thu, 4 Apr 2024 22:08:42 +0800	[thread overview]
Message-ID: <202404041408.434E8gIF2250814@localhost.localdomain> (raw)
In-Reply-To: <20240404142326.2151118-4-mtahhan@redhat.com>

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

_Compilation OK_

Submitter: Maryam Tahhan <mtahhan@redhat.com>
Date: Thu,  4 Apr 2024 10:23:20 -0400
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139097-139099 --> 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-04 14:33 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240404142326.2151118-4-mtahhan@redhat.com>
2024-04-04 14:08 ` qemudev [this message]
2024-04-04 14:13 ` qemudev
2024-04-04 14:25 ` |SUCCESS| pw139099 " checkpatch
2024-04-04 15:24 ` 0-day Robot
2024-04-04 16:53 ` |SUCCESS| pw139097-139099 [PATCH] [v13,3/3] net/af_xdp: support AF_X dpdklab
2024-04-04 16:55 ` dpdklab
2024-04-04 16:56 ` dpdklab
2024-04-04 16:57 ` dpdklab
2024-04-04 17:01 ` dpdklab
2024-04-04 17:22 ` dpdklab
2024-04-04 17:23 ` dpdklab
2024-04-04 17:23 ` dpdklab
2024-04-04 17:23 ` dpdklab
2024-04-04 17:24 ` dpdklab
2024-04-04 17:24 ` dpdklab
2024-04-04 17:24 ` dpdklab
2024-04-04 17:25 ` dpdklab
2024-04-04 17:25 ` dpdklab
2024-04-04 17:25 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:26 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:27 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:28 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:29 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:30 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:31 ` dpdklab
2024-04-04 17:32 ` dpdklab
2024-04-04 17:32 ` dpdklab
2024-04-04 17:33 ` dpdklab
2024-04-04 17:34 ` dpdklab
2024-04-04 17:34 ` dpdklab
2024-04-04 17:35 ` dpdklab
2024-04-04 17:35 ` dpdklab
2024-04-04 17:35 ` dpdklab
2024-04-04 17:36 ` dpdklab
2024-04-04 17:37 ` dpdklab
2024-04-04 17:38 ` dpdklab
2024-04-04 17:38 ` dpdklab
2024-04-04 17:38 ` dpdklab
2024-04-04 17:40 ` dpdklab
2024-04-04 17:40 ` dpdklab
2024-04-04 17:41 ` dpdklab
2024-04-04 17:42 ` dpdklab
2024-04-04 17:51 ` dpdklab
2024-04-04 17:54 ` dpdklab
2024-04-04 17:56 ` dpdklab
2024-04-04 17:59 ` dpdklab
2024-04-04 17:59 ` dpdklab
2024-04-04 18:02 ` dpdklab
2024-04-04 18:46 ` dpdklab
2024-04-04 18:47 ` dpdklab
2024-04-04 18:48 ` dpdklab
2024-04-04 21:19 ` dpdklab
2024-04-04 21:23 ` dpdklab
2024-04-04 21:27 ` dpdklab
2024-04-04 21:36 ` dpdklab
2024-04-04 21: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=202404041408.434E8gIF2250814@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).