automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133623 [PATCH] test/crypto: fix mbuf port in Rx inject
Date: Mon, 30 Oct 2023 14:26:05 +0800	[thread overview]
Message-ID: <202310300626.39U6Q5mH2976328@localhost.localdomain> (raw)
In-Reply-To: <20231030064542.3865749-1-rbhansali@marvell.com>

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

_Compilation OK_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Mon, 30 Oct 2023 12:15:42 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: ae142833dc14b386cde544fad58b88f337161a44

133623 --> 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-30  6:47 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231030064542.3865749-1-rbhansali@marvell.com>
2023-10-30  6:26 ` qemudev [this message]
2023-10-30  6:30 ` qemudev
2023-10-30  6:46 ` checkpatch
2023-10-30  7:21 dpdklab
2023-10-30  7:21 dpdklab
2023-10-30  7:21 dpdklab
2023-10-30  7:23 dpdklab
2023-10-30  7:30 dpdklab
2023-10-30  7:30 dpdklab
2023-10-30  7:31 dpdklab
2023-10-30  7:31 dpdklab
2023-10-30  7:31 dpdklab
2023-10-30  7:31 dpdklab
2023-10-30  7:32 dpdklab
2023-10-30  7:33 dpdklab
2023-10-30  7:33 dpdklab
2023-10-30  7:33 dpdklab
2023-10-30  7:33 dpdklab
2023-10-30  7:33 dpdklab
2023-10-30  7:34 dpdklab
2023-10-30  7:35 dpdklab
2023-10-30  7:35 dpdklab
2023-10-30  7:35 dpdklab
2023-10-30  7:35 dpdklab
2023-10-30  7:36 dpdklab
2023-10-30  7:36 dpdklab
2023-10-30  7:36 dpdklab
2023-10-30  7:36 dpdklab
2023-10-30  7:37 dpdklab
2023-10-30  7:37 dpdklab
2023-10-30  7:37 dpdklab
2023-10-30  7:38 dpdklab
2023-10-30  7:38 dpdklab
2023-10-30  7:38 dpdklab
2023-10-30  7:38 dpdklab
2023-10-30  7:38 dpdklab
2023-10-30  7:49 dpdklab
2023-10-30  7:53 dpdklab
2023-10-30  7:54 dpdklab
2023-10-30  7:55 dpdklab
2023-10-30  7:58 dpdklab
2023-10-30  7:58 dpdklab
2023-10-30  7:59 dpdklab
2023-10-30  7:59 dpdklab
2023-10-30  7:59 dpdklab
2023-10-30  8:01 dpdklab
2023-10-30  8:01 dpdklab
2023-10-30  8:02 dpdklab
2023-10-30  8:04 dpdklab
2023-10-30  8:06 dpdklab
2023-10-30  8:11 dpdklab
2023-10-30  8:11 dpdklab
2023-10-30  8:14 dpdklab
2023-10-30  8:18 dpdklab
2023-10-30  8:18 dpdklab
2023-10-30 10:07 dpdklab
2023-10-30 17:45 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=202310300626.39U6Q5mH2976328@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).