automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133627 [PATCH] devargs: fix derefrence before null test
Date: Mon, 30 Oct 2023 19:36:06 +0800	[thread overview]
Message-ID: <202310301136.39UBa6Xh3170207@localhost.localdomain> (raw)
In-Reply-To: <tencent_CF44B0629A79704E5F22C0749CBFED469809@qq.com>

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

_Compilation OK_

Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Mon, 30 Oct 2023 19:45:29 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 8fa22e1f79aae7dfc7a9eb77034e555e155e5e2a

133627 --> 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 11:57 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_CF44B0629A79704E5F22C0749CBFED469809@qq.com>
2023-10-30 11:36 ` qemudev [this message]
2023-10-30 11:40 ` qemudev
2023-10-30 11:47 ` |WARNING| " checkpatch
2023-10-30 13:55 ` |SUCCESS| " 0-day Robot
2023-10-30 14:30 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:31 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:32 dpdklab
2023-10-30 14:33 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:34 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:35 dpdklab
2023-10-30 14:36 dpdklab
2023-10-30 14:36 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:37 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:38 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:39 dpdklab
2023-10-30 14:40 dpdklab
2023-10-30 14:41 dpdklab
2023-10-30 14:42 dpdklab
2023-10-30 14:42 dpdklab
2023-10-30 14:43 dpdklab
2023-10-30 14:43 dpdklab
2023-10-30 14:44 dpdklab
2023-10-30 14:44 dpdklab
2023-10-30 14:45 dpdklab
2023-10-30 14:46 dpdklab
2023-10-30 14:47 dpdklab
2023-10-30 14:53 dpdklab
2023-10-30 15:01 dpdklab
2023-10-30 15:12 dpdklab
2023-10-30 15:35 dpdklab
2023-10-30 17:28 dpdklab
2023-10-30 22: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=202310301136.39UBa6Xh3170207@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).