automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131183 [PATCH] hash: fix SSE comparison
Date: Wed, 6 Sep 2023 10:18:49 +0800	[thread overview]
Message-ID: <202309060218.3862InxQ617401@localhost.localdomain> (raw)
In-Reply-To: <20230906023100.3618303-1-jieqiang.wang@arm.com>

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

_Compilation OK_

Submitter: Jieqiang Wang <jieqiang.wang@arm.com>
Date: Wed,  6 Sep 2023 10:31:00 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e92ba1426914db1d224dd5e9a1743657681b8814

131183 --> 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-09-06  2:33 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230906023100.3618303-1-jieqiang.wang@arm.com>
2023-09-06  2:18 ` qemudev [this message]
2023-09-06  2:22 ` qemudev
2023-09-06  2:32 ` checkpatch
2023-09-06  3:19 ` 0-day Robot
2023-09-06  3:20 dpdklab
2023-09-06  3:20 dpdklab
2023-09-06  3:20 dpdklab
2023-09-06  3:21 dpdklab
2023-09-06  3:22 dpdklab
2023-09-06  3:22 dpdklab
2023-09-06  3:23 dpdklab
2023-09-06  3:23 dpdklab
2023-09-06  3:25 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:28 dpdklab
2023-09-06  3:28 dpdklab
2023-09-06  3:31 dpdklab
2023-09-06  3:31 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:33 dpdklab
2023-09-06  3:34 dpdklab
2023-09-06  3:35 dpdklab
2023-09-06  3:38 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:50 dpdklab
2023-09-06  3:50 dpdklab
2023-09-06  3:51 dpdklab
2023-09-06  3:55 dpdklab
2023-09-06  3:55 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:57 dpdklab
2023-09-06  4:02 dpdklab
2023-09-06  4:03 dpdklab
2023-09-06  4:25 dpdklab
2023-09-06  4:31 dpdklab
2023-09-06  4:51 dpdklab
2023-09-06  7:23 dpdklab
2023-09-06  7:27 dpdklab
2023-09-06  7:32 dpdklab
2023-09-06  7:37 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=202309060218.3862InxQ617401@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).