automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124304 [PATCH v5] hash: add XOR32 hash function
Date: Wed, 22 Feb 2023 01:45:27 +0800	[thread overview]
Message-ID: <202302211745.31LHjRZq1251266@localhost.localdomain> (raw)
In-Reply-To: <20230221175529.644311-1-qobilidop@gmail.com>

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

_Compilation OK_

Submitter: Bili Dong <qobilidop@gmail.com>
Date: Tue, 21 Feb 2023 17:55:29 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 9bd5ebca59c865aead7096358fb733e53a72007b

124304 --> 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-02-21 17:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230221175529.644311-1-qobilidop@gmail.com>
2023-02-21 17:45 ` qemudev [this message]
2023-02-21 17:49 ` qemudev
2023-02-21 17:56 ` |WARNING| " checkpatch
2023-02-21 18:46 |SUCCESS| pw124304 [PATCH] [v5] " dpdklab
2023-02-21 19:16 dpdklab
2023-02-21 19:20 dpdklab
2023-02-21 19:20 dpdklab
2023-02-21 19:30 dpdklab
2023-02-21 19:31 dpdklab
2023-02-21 19:47 dpdklab
2023-02-21 19:55 dpdklab
2023-02-21 20:16 dpdklab
2023-02-22  1:09 dpdklab
2023-02-22  1:10 dpdklab
2023-02-22  1:16 dpdklab
2023-02-22  1:18 dpdklab
2023-02-22  1:19 dpdklab
2023-02-22  1:19 dpdklab
2023-02-22  1:20 dpdklab
2023-02-22  1:23 dpdklab
2023-02-22  1:28 dpdklab
2023-02-22  1:30 dpdklab
2023-02-22  1:31 dpdklab
2023-02-22  1:32 dpdklab
2023-02-22  1:32 dpdklab
2023-02-22  2:06 dpdklab
2023-02-23 15:19 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=202302211745.31LHjRZq1251266@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).