automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw119886 [PATCH] net/failsafe: Fix crash due to in-valid sub-device port id
Date: Wed, 16 Nov 2022 17:45:10 +0800	[thread overview]
Message-ID: <202211160945.2AG9jA141530276@localhost.localdomain> (raw)
In-Reply-To: <20221116095224.1576-1-madhuker.mythri@oracle.com>

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

_Compilation OK_

Submitter: Madhuker Mythri <madhuker.mythri@oracle.com>
Date: Wed, 16 Nov 2022 15:22:24 +0530
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 04f68bb92b6fee621ddf0f0948f5565fa31a84fd

119886 --> 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:[~2022-11-16  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221116095224.1576-1-madhuker.mythri@oracle.com>
2022-11-16  9:45 ` qemudev [this message]
2022-11-16  9:48 ` qemudev
2022-11-16  9:53 ` |WARNING| " checkpatch
2022-11-16 10:59 ` |SUCCESS| " 0-day Robot
2022-11-16 10:23 dpdklab
2022-11-16 10:26 dpdklab
2022-11-16 10:29 dpdklab
2022-11-16 10:32 dpdklab
2022-11-16 10:36 dpdklab
2022-11-16 10:48 dpdklab
2022-11-16 10:56 dpdklab
2022-11-16 12:16 dpdklab
2022-11-16 12:17 dpdklab
2022-11-16 12:42 dpdklab
2022-11-16 13:03 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=202211160945.2AG9jA141530276@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).