automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144249-144250 [RFC 4/4] ethdev: omit MAC address restore if not required
Date: Wed, 18 Sep 2024 16:57:16 +0800	[thread overview]
Message-ID: <202409180857.48I8vG953064495@localhost.localdomain> (raw)
In-Reply-To: <20240918092201.33772-5-dsosnowski@nvidia.com>

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

_Compilation OK_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wed, 18 Sep 2024 11:21:58 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 523fd7b3adfdf5a87651e8ca33bc69223b3211d5

144249-144250 --> 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-09-18  9:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240918092201.33772-5-dsosnowski@nvidia.com>
2024-09-18  8:57 ` qemudev [this message]
2024-09-18  9:01 ` qemudev
2024-09-18  9:24 ` |SUCCESS| pw144250 " checkpatch
2024-09-18 10:25 ` 0-day Robot
2024-09-18 20:22 ` |SUCCESS| pw144249-144250 [PATCH] [RFC,4/4] ethdev: omit MAC address dpdklab
2024-09-18 20:24 ` dpdklab
2024-09-18 20:44 ` dpdklab
2024-09-18 23:23 ` |PENDING| " dpdklab
2024-09-18 23:26 ` |SUCCESS| " dpdklab
2024-09-18 23:30 ` dpdklab
2024-09-18 23:44 ` dpdklab
2024-09-18 23:56 ` |PENDING| " dpdklab
2024-09-18 23:57 ` |SUCCESS| " dpdklab
2024-09-19  0:21 ` |PENDING| " dpdklab
2024-09-19  0:24 ` |SUCCESS| " dpdklab
2024-09-19  0:25 ` dpdklab
2024-09-19  1:07 ` dpdklab
2024-09-19  3:16 ` dpdklab
2024-09-19  4:38 ` dpdklab
2024-09-20  3:19 ` dpdklab
2024-09-22 18:39 ` dpdklab
2024-09-22 18:50 ` |FAILURE| " 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=202409180857.48I8vG953064495@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).