automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132097 [PATCH v3] net/af_xdp: fix missing UMEM feature
Date: Thu, 28 Sep 2023 17:08:01 +0800	[thread overview]
Message-ID: <202309280908.38S981ZJ3834576@localhost.localdomain> (raw)
In-Reply-To: <20230928092553.339452-1-shibin.koikkara.reeny@intel.com>

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

_Compilation OK_

Submitter: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
Date: Thu, 28 Sep 2023 09:25:53 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: b9e98c46e0e1d8490a86c663a0b9266fde1e3e80

132097 --> 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-28  9:29 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230928092553.339452-1-shibin.koikkara.reeny@intel.com>
2023-09-28  9:08 ` qemudev [this message]
2023-09-28  9:12 ` qemudev
2023-09-28  9:26 ` checkpatch
2023-09-28 10:19 ` 0-day Robot
2023-09-28 11:50 |SUCCESS| pw132097 [PATCH] [v3] " dpdklab
2023-09-28 11:50 dpdklab
2023-09-28 11:51 dpdklab
2023-09-28 11:51 dpdklab
2023-09-28 11:52 dpdklab
2023-09-28 11:52 dpdklab
2023-09-28 11:52 dpdklab
2023-09-28 11:52 dpdklab
2023-09-28 11:53 dpdklab
2023-09-28 11:53 dpdklab
2023-09-28 11:53 dpdklab
2023-09-28 11:53 dpdklab
2023-09-28 11:54 dpdklab
2023-09-28 11:54 dpdklab
2023-09-28 11:54 dpdklab
2023-09-28 11:54 dpdklab
2023-09-28 11:55 dpdklab
2023-09-28 11:55 dpdklab
2023-09-28 11:55 dpdklab
2023-09-28 11:55 dpdklab
2023-09-28 11:55 dpdklab
2023-09-28 11:56 dpdklab
2023-09-28 11:56 dpdklab
2023-09-28 11:56 dpdklab
2023-09-28 11:57 dpdklab
2023-09-28 11:57 dpdklab
2023-09-28 12:03 dpdklab
2023-09-28 12:10 dpdklab
2023-09-28 12:10 dpdklab
2023-09-28 12:12 dpdklab
2023-09-28 12:12 dpdklab
2023-09-28 12:12 dpdklab
2023-09-28 12:14 dpdklab
2023-09-28 12:14 dpdklab
2023-09-28 12:17 dpdklab
2023-09-28 12:18 dpdklab
2023-09-28 12:37 dpdklab
2023-09-28 12:38 dpdklab
2023-09-28 12:49 dpdklab
2023-09-28 12:50 dpdklab
2023-09-28 12:56 dpdklab
2023-09-28 13:00 dpdklab
2023-09-28 13:00 dpdklab
2023-09-28 13:04 dpdklab
2023-09-28 13:05 dpdklab
2023-09-28 13:06 dpdklab
2023-09-28 13:06 dpdklab
2023-09-28 13:10 dpdklab
2023-09-28 13:10 dpdklab
2023-09-28 13:19 dpdklab
2023-09-28 13:31 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=202309280908.38S981ZJ3834576@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).