automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138251-138281 [PATCH v4 31/31] net/ena: upgrade driver version to 2.9.0
Date: Wed, 13 Mar 2024 01:49:09 +0800	[thread overview]
Message-ID: <202403121749.42CHn9Tj3805212@localhost.localdomain> (raw)
In-Reply-To: <20240312180716.8515-32-shaibran@amazon.com>

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

_Compilation OK_

Submitter: Brandes, Shai <shaibran@amazon.com>
Date: Tue, 12 Mar 2024 20:06:46 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 544d6d79a6ff0964a79a57efb102e87fdbd107d9

138251-138281 --> 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-03-12 18:14 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312180716.8515-32-shaibran@amazon.com>
2024-03-12 17:49 ` qemudev [this message]
2024-03-12 17:53 ` qemudev
2024-03-12 18:12 ` |SUCCESS| pw138281 " checkpatch
2024-03-12 19:03 ` 0-day Robot
2024-03-12 22:26 ` |SUCCESS| pw138251-138281 [PATCH] [v4,31/31] net/ena: upgrade driver dpdklab
2024-03-12 22:27 ` dpdklab
2024-03-12 22:36 ` dpdklab
2024-03-12 22:36 ` dpdklab
2024-03-12 22:37 ` dpdklab
2024-03-12 22:38 ` dpdklab
2024-03-12 22:38 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-12 22:40 ` dpdklab
2024-03-12 22:41 ` dpdklab
2024-03-12 22:41 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:44 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:59 ` dpdklab
2024-03-12 23:00 ` dpdklab
2024-03-12 23:01 ` dpdklab
2024-03-12 23:02 ` dpdklab
2024-03-12 23:03 ` dpdklab
2024-03-12 23:03 ` dpdklab
2024-03-12 23:04 ` dpdklab
2024-03-12 23:04 ` dpdklab
2024-03-12 23:04 ` dpdklab
2024-03-12 23:05 ` dpdklab
2024-03-12 23:05 ` dpdklab
2024-03-12 23:07 ` dpdklab
2024-03-12 23:08 ` dpdklab
2024-03-12 23:08 ` dpdklab
2024-03-12 23:08 ` dpdklab
2024-03-12 23:09 ` dpdklab
2024-03-12 23:09 ` dpdklab
2024-03-12 23:09 ` dpdklab
2024-03-12 23:09 ` dpdklab
2024-03-12 23:10 ` dpdklab
2024-03-12 23:10 ` dpdklab
2024-03-12 23:10 ` dpdklab
2024-03-12 23:11 ` dpdklab
2024-03-12 23:11 ` dpdklab
2024-03-12 23:11 ` dpdklab
2024-03-12 23:12 ` dpdklab
2024-03-12 23:12 ` dpdklab
2024-03-12 23:12 ` dpdklab
2024-03-12 23:12 ` dpdklab
2024-03-12 23:12 ` dpdklab
2024-03-12 23:13 ` dpdklab
2024-03-12 23:14 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-13  0:23 ` dpdklab
2024-03-13  0:26 ` dpdklab
2024-03-13  0:34 ` dpdklab
2024-03-13  0:37 ` dpdklab
2024-03-13  1:15 ` dpdklab
2024-03-13  1:44 ` dpdklab
2024-03-16 13:43 ` dpdklab
2024-03-16 14:19 ` 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=202403121749.42CHn9Tj3805212@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).