automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138066-138070 [PATCH v3 5/5] net/cxgbe: use rte macro instead of GCC attribute
Date: Thu, 7 Mar 2024 06:02:05 +0800	[thread overview]
Message-ID: <202403062202.426M25do3596718@localhost.localdomain> (raw)
In-Reply-To: <1709763287-10713-6-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed,  6 Mar 2024 14:14:43 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2a454f84f715608ee709a4c6ba00edf2e4b62b69

138066-138070 --> 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-06 22:26 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709763287-10713-6-git-send-email-roretzla@linux.microsoft.com>
2024-03-06 22:02 ` qemudev [this message]
2024-03-06 22:06 ` qemudev
2024-03-06 22:15 ` |WARNING| pw138070 " checkpatch
2024-03-06 23:04 ` |SUCCESS| " 0-day Robot
2024-03-07  3:10 ` |SUCCESS| pw138066-138070 [PATCH] [v3,5/5] net/cxgbe: use rte macro dpdklab
2024-03-07  3:14 ` dpdklab
2024-03-07  3:14 ` dpdklab
2024-03-07  3:16 ` dpdklab
2024-03-07  3:28 ` dpdklab
2024-03-07  3:30 ` dpdklab
2024-03-07  3:31 ` dpdklab
2024-03-07  3:32 ` dpdklab
2024-03-07  3:33 ` dpdklab
2024-03-07  3:33 ` dpdklab
2024-03-07  3:33 ` dpdklab
2024-03-07  3:39 ` dpdklab
2024-03-07  3:43 ` dpdklab
2024-03-07  3:44 ` dpdklab
2024-03-07  3:44 ` dpdklab
2024-03-07  3:44 ` dpdklab
2024-03-07  3:45 ` dpdklab
2024-03-07  3:45 ` dpdklab
2024-03-07  3:46 ` dpdklab
2024-03-07  3:46 ` dpdklab
2024-03-07  3:47 ` dpdklab
2024-03-07  3:54 ` dpdklab
2024-03-07  3:55 ` dpdklab
2024-03-07  3:55 ` dpdklab
2024-03-07  3:55 ` dpdklab
2024-03-07  3:56 ` dpdklab
2024-03-07  3:57 ` dpdklab
2024-03-07  3:57 ` dpdklab
2024-03-07  3:57 ` dpdklab
2024-03-07  3:58 ` dpdklab
2024-03-07  3:59 ` dpdklab
2024-03-07  4:00 ` dpdklab
2024-03-07  4:00 ` dpdklab
2024-03-07  4:01 ` dpdklab
2024-03-07  4:01 ` dpdklab
2024-03-07  4:02 ` dpdklab
2024-03-07  4:02 ` dpdklab
2024-03-07  4:03 ` dpdklab
2024-03-07  4:03 ` dpdklab
2024-03-07  4:03 ` dpdklab
2024-03-07  4:04 ` dpdklab
2024-03-07  4:04 ` dpdklab
2024-03-07  4:07 ` dpdklab
2024-03-07  4:09 ` dpdklab
2024-03-07  4:10 ` dpdklab
2024-03-07  4:11 ` dpdklab
2024-03-07  4:14 ` dpdklab
2024-03-07  4:16 ` dpdklab
2024-03-07  4:16 ` dpdklab
2024-03-07  4:19 ` dpdklab
2024-03-07  4:19 ` dpdklab
2024-03-07  4:25 ` dpdklab
2024-03-07  4:32 ` dpdklab
2024-03-07  4:35 ` dpdklab
2024-03-07  4:35 ` dpdklab
2024-03-07  4:48 ` dpdklab
2024-03-07  4:49 ` dpdklab
2024-03-07  4:52 ` dpdklab
2024-03-07  5:11 ` dpdklab
2024-03-07  5:18 ` dpdklab
2024-03-07  5:26 ` dpdklab
2024-03-07  5:47 ` dpdklab
2024-03-07  6:29 ` dpdklab
2024-03-07  6:55 ` dpdklab
2024-03-08  1:11 ` dpdklab
2024-03-08  1:24 ` dpdklab
2024-03-08  1:25 ` dpdklab
2024-03-08  1:27 ` 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=202403062202.426M25do3596718@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).