automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138435 [PATCH] windows: make getopt functions have const properties
Date: Fri, 15 Mar 2024 22:51:02 +0800	[thread overview]
Message-ID: <202403151451.42FEp2261936510@localhost.localdomain> (raw)
In-Reply-To: <20240315151407.7517-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 15 Mar 2024 08:14:06 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 90a91f8761af9f99243e1ca35082fcf05ff7a9b2

138435 --> 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-15 15:16 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240315151407.7517-1-stephen@networkplumber.org>
2024-03-15 14:51 ` qemudev [this message]
2024-03-15 14:55 ` qemudev
2024-03-15 15:15 ` |WARNING| " checkpatch
2024-03-15 16:03 ` |SUCCESS| " 0-day Robot
2024-03-16  5:49 ` |SUCCESS| pw138435 [PATCH] windows: make getopt functions have const dpdklab
2024-03-16  5:52 ` dpdklab
2024-03-16  5:53 ` dpdklab
2024-03-16  5:56 ` dpdklab
2024-03-16  5:58 ` dpdklab
2024-03-16  5:59 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:17 ` dpdklab
2024-03-16  6:24 ` dpdklab
2024-03-16  6:24 ` dpdklab
2024-03-16  6:26 ` dpdklab
2024-03-16  6:26 ` dpdklab
2024-03-16  6:27 ` dpdklab
2024-03-16  6:30 ` dpdklab
2024-03-16  6:31 ` dpdklab
2024-03-16  6:32 ` dpdklab
2024-03-16  6:32 ` dpdklab
2024-03-16  6:32 ` dpdklab
2024-03-16  6:33 ` dpdklab
2024-03-16  6:33 ` dpdklab
2024-03-16  6:34 ` dpdklab
2024-03-16  6:35 ` dpdklab
2024-03-16  6:35 ` dpdklab
2024-03-16  6:40 ` dpdklab
2024-03-16  6:41 ` dpdklab
2024-03-16  6:41 ` dpdklab
2024-03-16  6:42 ` dpdklab
2024-03-16  6:42 ` dpdklab
2024-03-16  6:42 ` dpdklab
2024-03-16  6:42 ` dpdklab
2024-03-16  6:43 ` dpdklab
2024-03-16  6:43 ` dpdklab
2024-03-16  6:43 ` dpdklab
2024-03-16  6:43 ` dpdklab
2024-03-16  6:44 ` dpdklab
2024-03-16  6:44 ` dpdklab
2024-03-16  6:44 ` dpdklab
2024-03-16  6:45 ` dpdklab
2024-03-16  6:45 ` dpdklab
2024-03-16  6:45 ` dpdklab
2024-03-16  6:45 ` dpdklab
2024-03-16  6:46 ` dpdklab
2024-03-16  7:06 ` dpdklab
2024-03-16  7:06 ` dpdklab
2024-03-16  7:07 ` dpdklab
2024-03-16  7:07 ` dpdklab
2024-03-16  7:07 ` dpdklab
2024-03-16  7:07 ` dpdklab
2024-03-16  7:09 ` dpdklab
2024-03-16  7:10 ` dpdklab
2024-03-16  7:13 ` dpdklab
2024-03-16  7:13 ` dpdklab
2024-03-16  7:15 ` dpdklab
2024-03-16  7:16 ` dpdklab
2024-03-16  7:17 ` dpdklab
2024-03-16  7:17 ` dpdklab
2024-03-16  7:18 ` dpdklab
2024-03-16  7:19 ` dpdklab
2024-03-16  7:21 ` dpdklab
2024-03-16  7:23 ` dpdklab
2024-03-16  7:23 ` dpdklab
2024-03-16  7:24 ` dpdklab
2024-03-16  7:24 ` dpdklab
2024-03-16  7:25 ` dpdklab
2024-03-16  7:26 ` dpdklab
2024-03-16  7:28 ` dpdklab
2024-03-16  7:28 ` dpdklab
2024-03-16  7:29 ` dpdklab
2024-03-16  7:32 ` dpdklab
2024-03-16  7:54 ` dpdklab
2024-03-16  7:56 ` dpdklab
2024-03-16  9:19 ` dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 18:24 ` 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=202403151451.42FEp2261936510@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).