automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132462 [PATCH v2] ethdev: add calculate hash function
Date: Tue, 10 Oct 2023 22:06:35 +0800	[thread overview]
Message-ID: <202310101406.39AE6ZNR2678344@localhost.localdomain> (raw)
In-Reply-To: <20231010142401.27289-1-orika@nvidia.com>

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

_Compilation OK_

Submitter: Ori Kam <orika@nvidia.com>
Date: Tue, 10 Oct 2023 17:24:01 +0300
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: f7455db8795464600bf50c1173af095a69c18a75

132462 --> 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-10-10 14:27 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231010142401.27289-1-orika@nvidia.com>
2023-10-10 14:06 ` qemudev [this message]
2023-10-10 14:10 ` qemudev
2023-10-10 14:26 ` |WARNING| " checkpatch
2023-10-10 20:54 |SUCCESS| pw132462 [PATCH] [v2] " dpdklab
2023-10-10 20:55 dpdklab
2023-10-10 20:58 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:20 dpdklab
2023-10-10 21:24 dpdklab
2023-10-11  1:07 dpdklab
2023-10-11  1:21 dpdklab
2023-10-11  1:53 dpdklab
2023-10-11  2:31 dpdklab
2023-10-11  2:33 dpdklab
2023-10-11  2:34 dpdklab
2023-10-11  2:35 dpdklab
2023-10-11  2:36 dpdklab
2023-10-11  2:37 dpdklab
2023-10-11  2:37 dpdklab
2023-10-11  2:40 dpdklab
2023-10-11  2:41 dpdklab
2023-10-11  2:42 dpdklab
2023-10-11  2:43 dpdklab
2023-10-11  2:44 dpdklab
2023-10-11  2:45 dpdklab
2023-10-11  2:46 dpdklab
2023-10-11  2:47 dpdklab
2023-10-11  2:47 dpdklab
2023-10-11  2:54 dpdklab
2023-10-11  2:54 dpdklab
2023-10-11  2:55 dpdklab
2023-10-11  2:55 dpdklab
2023-10-11  2:55 dpdklab
2023-10-11  2:56 dpdklab
2023-10-11  2:56 dpdklab
2023-10-11  2:57 dpdklab
2023-10-11  2:57 dpdklab
2023-10-11  3:00 dpdklab
2023-10-11  3:01 dpdklab
2023-10-11  3:03 dpdklab
2023-10-11  3:18 dpdklab
2023-10-11  3:19 dpdklab
2023-10-11  3:21 dpdklab
2023-10-11  3:21 dpdklab
2023-10-11  3:22 dpdklab
2023-10-11  3:56 dpdklab
2023-10-11 10:38 dpdklab
2023-10-12  1:28 dpdklab
2023-10-12  2:39 dpdklab
2023-10-12  2:52 dpdklab
2023-10-12  2:52 dpdklab
2023-10-12  2:54 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=202310101406.39AE6ZNR2678344@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).