automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122985 [PATCH v2 1/1] compress/octeontx: support scatter gather mode
Date: Fri, 3 Feb 2023 11:58:53 +0800	[thread overview]
Message-ID: <202302030358.3133wrAm152847@localhost.localdomain> (raw)
In-Reply-To: <20230203022100.3364599-1-mchalla@marvell.com>

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

_Compilation OK_

Submitter: Mahipal Challa <mchalla@marvell.com>
Date: Fri, 3 Feb 2023 07:51:00 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: bb78d241b04edfa0357041c46dce33f9edb42b20

122985 --> 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


  parent reply	other threads:[~2023-02-03  4:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230203022100.3364599-1-mchalla@marvell.com>
2023-02-03  2:22 ` |WARNING| " checkpatch
2023-02-03  3:42 ` |SUCCESS| pw122985 [dpdk-dev] " 0-day Robot
2023-02-03  3:58 ` qemudev [this message]
2023-02-03  4:02 ` |SUCCESS| pw122985 " qemudev
2023-02-03  3:01 |SUCCESS| pw122985 [PATCH] [v2, " dpdklab
2023-02-03  3:18 dpdklab
2023-02-03  3:41 dpdklab
2023-02-03  3:42 dpdklab
2023-02-03  3:53 dpdklab
2023-02-03  3:57 dpdklab
2023-02-03  4:13 dpdklab
2023-02-03  7:03 dpdklab
2023-02-04  4:46 dpdklab
2023-02-04  5:32 dpdklab
2023-02-04  6:08 dpdklab
2023-02-04  6:08 dpdklab
2023-02-04  6:08 dpdklab
2023-02-04  6:08 dpdklab
2023-02-04  6:27 dpdklab
2023-02-04  6:31 dpdklab
2023-02-04  6:31 dpdklab
2023-02-04  6:31 dpdklab
2023-02-04  6:31 dpdklab
2023-02-05  4:16 dpdklab
2023-02-05 14:40 dpdklab
2023-02-05 17:26 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=202302030358.3133wrAm152847@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).