automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140229-140236 [PATCH v9 8/8] net/null: use generic SW stats
Date: Wed, 22 May 2024 03:56:28 +0800	[thread overview]
Message-ID: <202405211956.44LJuSUx775841@localhost.localdomain> (raw)
In-Reply-To: <20240521201801.126886-9-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 21 May 2024 13:16:34 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 6f80df8cb0f889203d7cd27766abcc6ebc720e33

140229-140236 --> 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-05-21 20:25 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240521201801.126886-9-stephen@networkplumber.org>
2024-05-21 19:56 ` qemudev [this message]
2024-05-21 20:00 ` qemudev
2024-05-21 20:21 ` |SUCCESS| pw140236 " checkpatch
2024-05-21 21:24 ` |FAILURE| " 0-day Robot
2024-05-21 21:25 ` |SUCCESS| pw140229-140236 [PATCH] [v9,8/8] net/null: use generic SW dpdklab
2024-05-21 21:25 ` dpdklab
2024-05-21 21:26 ` dpdklab
2024-05-21 21:26 ` dpdklab
2024-05-21 21:26 ` dpdklab
2024-05-21 21:27 ` dpdklab
2024-05-21 21:34 ` dpdklab
2024-05-21 21:34 ` dpdklab
2024-05-21 21:35 ` dpdklab
2024-05-21 21:35 ` dpdklab
2024-05-21 21:35 ` dpdklab
2024-05-21 21:36 ` dpdklab
2024-05-21 21:36 ` dpdklab
2024-05-21 21:36 ` dpdklab
2024-05-21 21:37 ` dpdklab
2024-05-21 21:37 ` dpdklab
2024-05-21 21:38 ` dpdklab
2024-05-21 21:38 ` dpdklab
2024-05-21 21:38 ` dpdklab
2024-05-21 21:39 ` dpdklab
2024-05-21 21:39 ` dpdklab
2024-05-21 21:39 ` dpdklab
2024-05-21 21:39 ` dpdklab
2024-05-21 21:39 ` dpdklab
2024-05-21 21:40 ` dpdklab
2024-05-21 21:40 ` dpdklab
2024-05-21 21:40 ` dpdklab
2024-05-21 21:41 ` dpdklab
2024-05-21 21:41 ` dpdklab
2024-05-21 21:41 ` dpdklab
2024-05-21 21:41 ` dpdklab
2024-05-21 21:42 ` dpdklab
2024-05-21 21:42 ` dpdklab
2024-05-21 21:42 ` dpdklab
2024-05-21 21:42 ` dpdklab
2024-05-21 21:42 ` dpdklab
2024-05-21 21:43 ` dpdklab
2024-05-21 21:43 ` dpdklab
2024-05-21 21:43 ` dpdklab
2024-05-21 21:43 ` dpdklab
2024-05-21 21:44 ` dpdklab
2024-05-21 21:44 ` dpdklab
2024-05-21 21:44 ` dpdklab
2024-05-21 21:45 ` dpdklab
2024-05-21 21:45 ` dpdklab
2024-05-21 21:45 ` dpdklab
2024-05-21 21:45 ` dpdklab
2024-05-21 21:46 ` dpdklab
2024-05-21 21:46 ` dpdklab
2024-05-21 21:47 ` dpdklab
2024-05-21 21:49 ` dpdklab
2024-05-21 21:50 ` dpdklab
2024-05-21 21:50 ` dpdklab
2024-05-21 21:50 ` dpdklab
2024-05-21 21:51 ` dpdklab
2024-05-21 21:51 ` dpdklab
2024-05-21 21:51 ` dpdklab
2024-05-21 21:52 ` dpdklab
2024-05-21 21:52 ` dpdklab
2024-05-21 21:53 ` dpdklab
2024-05-21 21:53 ` dpdklab
2024-05-21 21:54 ` dpdklab
2024-05-21 21:55 ` dpdklab
2024-05-21 21:55 ` dpdklab
2024-05-21 21:56 ` dpdklab
2024-05-21 21:56 ` dpdklab
2024-05-21 21:57 ` dpdklab
2024-05-21 21:57 ` dpdklab
2024-05-21 21:58 ` dpdklab
2024-05-21 21:58 ` dpdklab
2024-05-21 22:00 ` dpdklab
2024-05-21 22:01 ` dpdklab
2024-05-21 22:01 ` dpdklab
2024-05-21 22:02 ` dpdklab
2024-05-21 22:03 ` dpdklab
2024-05-21 22:04 ` dpdklab
2024-05-21 22:24 ` dpdklab
2024-05-21 22:33 ` dpdklab
2024-05-21 22:34 ` dpdklab
2024-05-21 22:39 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-23  6:05 ` 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=202405211956.44LJuSUx775841@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).