automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146854 [PATCH v2 1/1] event/octeontx: resolve possible integer overflow
Date: Wed, 23 Oct 2024 15:28:25 +0800	[thread overview]
Message-ID: <202410230728.49N7SPpm305290@localhost.localdomain> (raw)
In-Reply-To: <20241023071546.865609-1-hpothula@marvell.com>

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

_Compilation OK_

Submitter: Hanumanth Pothula <hpothula@marvell.com>
Date: Wed, 23 Oct 2024 12:45:46 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: 920fc013f4264b9d231f64fc934e6633e6ac4fb8

146854 --> 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:[~2024-10-23  8:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241023071546.865609-1-hpothula@marvell.com>
2024-10-23  7:16 ` checkpatch
2024-10-23  7:28 ` qemudev [this message]
2024-10-23  7:33 ` qemudev
2024-10-23  8:06 ` 0-day Robot
2024-10-23 11:13 ` |SUCCESS| pw146854 [PATCH] [v2,1/1] event/octeontx: resolve possible dpdklab
2024-10-23 14:57 ` dpdklab
2024-10-23 15:34 ` dpdklab
2024-10-23 16:22 ` dpdklab
2024-10-23 17:49 ` dpdklab
2024-10-24  1:36 ` dpdklab
2024-10-24  2:13 ` dpdklab
2024-10-25  3:28 ` |PENDING| " dpdklab
2024-10-25  5:14 ` dpdklab
2024-10-26  0:28 ` |SUCCESS| " dpdklab
2024-10-26  2:26 ` |PENDING| " dpdklab
2024-10-27 12:56 ` |SUCCESS| " dpdklab
2024-11-01 23:19 ` dpdklab
2024-11-02 21:33 ` 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=202410230728.49N7SPpm305290@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).