automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138072 [PATCH v3] hash: put GFNI stubs back
Date: Thu, 7 Mar 2024 09:14:34 +0800	[thread overview]
Message-ID: <202403070114.4271EYYq3660837@localhost.localdomain> (raw)
In-Reply-To: <20240307013715.114013-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed,  6 Mar 2024 17:36:42 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2a454f84f715608ee709a4c6ba00edf2e4b62b69

138072 --> 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-07  1:39 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307013715.114013-1-stephen@networkplumber.org>
2024-03-07  1:14 ` qemudev [this message]
2024-03-07  1:19 ` qemudev
2024-03-07  1:38 ` checkpatch
2024-03-07  2:15 ` |SUCCESS| pw138072 [PATCH] [v3] " dpdklab
2024-03-07  2:15 ` dpdklab
2024-03-07  2:15 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:16 ` dpdklab
2024-03-07  2:17 ` dpdklab
2024-03-07  2:18 ` dpdklab
2024-03-07  2:24 ` |FAILURE| pw138072 [PATCH v3] " 0-day Robot
2024-03-07  2:25 ` |SUCCESS| pw138072 [PATCH] [v3] " dpdklab
2024-03-07  2:26 ` dpdklab
2024-03-07  2:26 ` dpdklab
2024-03-07  2:27 ` dpdklab
2024-03-07  2:27 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:28 ` dpdklab
2024-03-07  2:29 ` dpdklab
2024-03-07  2:30 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:32 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:33 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:34 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:35 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:36 ` dpdklab
2024-03-07  2:37 ` dpdklab
2024-03-07  2:39 ` dpdklab
2024-03-07  2:43 ` dpdklab
2024-03-07  2:44 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:45 ` dpdklab
2024-03-07  2:49 ` dpdklab
2024-03-07  3:01 ` dpdklab
2024-03-07  3:01 ` dpdklab
2024-03-07  3:05 ` dpdklab
2024-03-07  3:06 ` dpdklab
2024-03-07  3:06 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:07 ` dpdklab
2024-03-07  3:08 ` dpdklab
2024-03-07  3:08 ` dpdklab
2024-03-07  3:09 ` dpdklab
2024-03-07  3:09 ` dpdklab
2024-03-07  3:12 ` dpdklab
2024-03-07  3:14 ` dpdklab
2024-03-07  3:45 ` dpdklab
2024-03-07  4:00 ` dpdklab
2024-03-08  0:29 ` dpdklab
2024-03-08  0:34 ` dpdklab
2024-03-08  0:38 ` dpdklab
2024-03-08  0:44 ` 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=202403070114.4271EYYq3660837@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).