automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124549 [PATCH] net/mlx5: reject flow template API reconfiguration
Date: Sun, 26 Feb 2023 03:46:54 +0800	[thread overview]
Message-ID: <202302251946.31PJks3Z4011201@localhost.localdomain> (raw)
In-Reply-To: <20230225195804.3581-1-dsosnowski@nvidia.com>

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

_Compilation OK_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Sat, 25 Feb 2023 19:58:04 +0000
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 34c8d1d3bef546f03159407a7af314176456d629

124549 --> 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-02-25 20:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230225195804.3581-1-dsosnowski@nvidia.com>
2023-02-25 19:46 ` qemudev [this message]
2023-02-25 19:50 ` qemudev
2023-02-25 19:58 ` checkpatch
2023-02-25 22:39 ` 0-day Robot
2023-02-27 16:28 dpdklab
2023-02-27 16:29 dpdklab
2023-02-27 16:32 dpdklab
2023-02-27 16:36 dpdklab
2023-02-27 16:40 dpdklab
2023-02-27 16:52 dpdklab
2023-02-27 16:56 dpdklab
2023-02-27 17:01 dpdklab
2023-02-27 17:06 dpdklab
2023-02-27 17:08 dpdklab
2023-02-27 17:22 dpdklab
2023-02-27 18:00 dpdklab
2023-02-27 18:28 dpdklab
2023-02-27 18:33 dpdklab
2023-02-27 18:34 dpdklab
2023-02-27 18:36 dpdklab
2023-02-27 18:36 dpdklab
2023-02-27 18:39 dpdklab
2023-02-27 18:41 dpdklab
2023-02-27 18:41 dpdklab
2023-02-27 18:44 dpdklab
2023-02-27 18:50 dpdklab
2023-02-27 18:53 dpdklab
2023-02-27 18:53 dpdklab
2023-02-27 20:14 dpdklab
2023-02-27 20:29 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=202302251946.31PJks3Z4011201@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).