automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125418 [PATCH] net/mlx5/hws: fix saving of jumbo tag for deletion
Date: Thu, 23 Mar 2023 14:14:55 +0800	[thread overview]
Message-ID: <202303230614.32N6EtFR502991@localhost.localdomain> (raw)
In-Reply-To: <20230322101621.642765-3-erezsh@nvidia.com>

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

_Compilation OK_

Submitter: Erez Shitrit <erezsh@nvidia.com>
Date: Wed, 22 Mar 2023 12:16:20 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 33949800f1afcb7527b6e36c60c1548687ccb673

125418 --> 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


  parent reply	other threads:[~2023-03-23  6:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230322101621.642765-3-erezsh@nvidia.com>
2023-03-22 10:17 ` checkpatch
2023-03-22 12:39 ` 0-day Robot
2023-03-23  6:14 ` qemudev [this message]
2023-03-23  6:15 ` qemudev
2023-03-24  9:11 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24  0:37 dpdklab
2023-03-23  8:30 dpdklab
2023-03-22 23:28 dpdklab
2023-03-22 21:45 dpdklab
2023-03-22 20:06 dpdklab
2023-03-22 19:59 dpdklab
2023-03-22 19:54 dpdklab
2023-03-22 19:50 dpdklab
2023-03-22 19:45 dpdklab
2023-03-22 19:43 dpdklab
2023-03-22 19:41 dpdklab
2023-03-22 19:33 dpdklab
2023-03-22 19:30 dpdklab
2023-03-22 19:30 dpdklab
2023-03-22 19:29 dpdklab
2023-03-22 19:17 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=202303230614.32N6EtFR502991@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).