automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw119885 [PATCH] net/mlx5: fix GENEVE resource management
Date: Wed, 16 Nov 2022 17:29:01 +0800	[thread overview]
Message-ID: <202211160929.2AG9T1Dh1478705@localhost.localdomain> (raw)
In-Reply-To: <20221116093654.19165-1-suanmingm@nvidia.com>

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

_Compilation OK_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Wed, 16 Nov 2022 11:36:54 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 04f68bb92b6fee621ddf0f0948f5565fa31a84fd

119885 --> 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:[~2022-11-16  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221116093654.19165-1-suanmingm@nvidia.com>
2022-11-16  9:29 ` qemudev [this message]
2022-11-16  9:33 ` qemudev
2022-11-16  9:38 ` checkpatch
2022-11-16 10:39 ` 0-day Robot
2022-11-16 11:56 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-11-16 11:13 dpdklab
2022-11-16 11:03 dpdklab
2022-11-16 10:33 dpdklab
2022-11-16 10:29 dpdklab
2022-11-16 10:25 dpdklab
2022-11-16 10:22 dpdklab
2022-11-16 10:15 dpdklab
2022-11-16 10:14 dpdklab
2022-11-16 10:10 dpdklab
2022-11-16 10:09 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=202211160929.2AG9T1Dh1478705@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).