automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137407-137409 [PATCH v3 6/6] table: replace zero length array with flex array
Date: Wed, 28 Feb 2024 07:34:31 +0800	[thread overview]
Message-ID: <202402272334.41RNYVGf492410@localhost.localdomain> (raw)
In-Reply-To: <1709078215-20292-7-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 27 Feb 2024 15:56:50 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137407-137409 --> 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-02-28  0:00 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709078215-20292-7-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 23:34 ` qemudev [this message]
2024-02-27 23:38 ` qemudev
2024-02-27 23:58 ` |SUCCESS| pw137409 " checkpatch
2024-02-28  0:45 ` |FAILURE| " 0-day Robot
2024-02-28  8:07 ` |SUCCESS| pw137407-137409 [PATCH] [v3,6/6] table: replace zero lengt dpdklab
2024-02-28  8:08 ` dpdklab
2024-02-28  8:10 ` |WARNING| " dpdklab
2024-02-28  8:12 ` |SUCCESS| " dpdklab
2024-02-28  8:13 ` dpdklab
2024-02-28  8:14 ` dpdklab
2024-02-28  8:24 ` |WARNING| " dpdklab
2024-02-28  8:25 ` dpdklab
2024-02-28  8:26 ` dpdklab
2024-02-28  8:26 ` |SUCCESS| " dpdklab
2024-02-28  8:26 ` |WARNING| " dpdklab
2024-02-28  8:26 ` dpdklab
2024-02-28  8:26 ` |SUCCESS| " dpdklab
2024-02-28  8:29 ` |WARNING| " dpdklab
2024-02-28  8:35 ` |SUCCESS| " dpdklab
2024-02-28  8:36 ` |WARNING| " dpdklab
2024-02-28  8:38 ` dpdklab
2024-02-28  8:39 ` |SUCCESS| " dpdklab
2024-02-28  8:39 ` dpdklab
2024-02-28  8:40 ` dpdklab
2024-02-28  8:44 ` dpdklab
2024-02-28  8:44 ` dpdklab
2024-02-28  8:44 ` dpdklab
2024-02-28  8:45 ` dpdklab
2024-02-28  8:45 ` dpdklab
2024-02-28  8:45 ` dpdklab
2024-02-28  8:47 ` dpdklab
2024-02-28  8:47 ` dpdklab
2024-02-28  8:47 ` dpdklab
2024-02-28  8:48 ` dpdklab
2024-02-28  8:48 ` dpdklab
2024-02-28  8:48 ` dpdklab
2024-02-28  8:48 ` dpdklab
2024-02-28  8:49 ` dpdklab
2024-02-28  8:50 ` dpdklab
2024-02-28  8:51 ` dpdklab
2024-02-28  8:51 ` dpdklab
2024-02-28  8:52 ` dpdklab
2024-02-28  8:53 ` dpdklab
2024-02-28  8:54 ` dpdklab
2024-02-28  8:57 ` dpdklab
2024-02-28  8:58 ` dpdklab
2024-02-28  9:00 ` dpdklab
2024-02-28  9:03 ` dpdklab
2024-02-28  9:05 ` dpdklab
2024-02-28  9:07 ` dpdklab
2024-02-28  9:12 ` dpdklab
2024-02-28  9:15 ` dpdklab
2024-02-28  9:19 ` dpdklab
2024-02-28  9:22 ` dpdklab
2024-02-28  9:23 ` dpdklab
2024-02-28  9:25 ` dpdklab
2024-02-28  9:26 ` dpdklab
2024-02-28  9:27 ` dpdklab
2024-02-28  9:32 ` dpdklab
2024-02-28  9:54 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 16:59 ` dpdklab
2024-02-28 17:06 ` dpdklab
2024-02-29  5:17 ` dpdklab
2024-02-29 19:54 ` dpdklab
2024-02-29 19:57 ` dpdklab
2024-02-29 19:59 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-03-01  5:38 ` dpdklab
2024-03-01  6:00 ` dpdklab
2024-03-01  6:35 ` 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=202402272334.41RNYVGf492410@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).