automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129755 [PATCH] cmdline: remove cmdline_poll()
Date: Tue, 1 Aug 2023 00:01:12 +0800	[thread overview]
Message-ID: <202307311601.36VG1CDc410484@localhost.localdomain> (raw)
In-Reply-To: <20230731161232.180420-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 31 Jul 2023 09:12:32 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 0ae35eceb9e4569b0814fcf671b4455301bb7518

129755 --> 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:[~2023-07-31 16:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230731161232.180420-1-stephen@networkplumber.org>
2023-07-31 16:01 ` qemudev [this message]
2023-07-31 16:05 ` qemudev
2023-07-31 16:13 ` |SUCCESS| pw129755 [PATCH] cmdline: remove cmdline_poll checkpatch
2023-07-31 20:18 ` |SUCCESS| pw129755 [PATCH] cmdline: remove cmdline_poll() 0-day Robot
2023-08-01  2:46 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-08-01  2:45 dpdklab
2023-07-31 23:17 dpdklab
2023-07-31 23:13 dpdklab
2023-07-31 23:08 dpdklab
2023-07-31 22:58 dpdklab
2023-07-31 22:53 dpdklab
2023-07-31 21:16 dpdklab
2023-07-31 19:02 dpdklab
2023-07-31 18:16 dpdklab
2023-07-31 18:08 dpdklab
2023-07-31 18:08 dpdklab
2023-07-31 18:08 dpdklab
2023-07-31 18:08 dpdklab
2023-07-31 18:07 dpdklab
2023-07-31 18:06 dpdklab
2023-07-31 18:06 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=202307311601.36VG1CDc410484@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).