automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120546 [PATCH] net/idpf: fix build option check
Date: Fri, 9 Dec 2022 00:41:46 +0800	[thread overview]
Message-ID: <202212081641.2B8GfkSJ197648@localhost.localdomain> (raw)
In-Reply-To: <20221208033127.57161-1-jingjing.wu@intel.com>

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

_Compilation OK_

Submitter: Jingjing Wu <jingjing.wu@intel.com>
Date: Thu,  8 Dec 2022 03:31:27 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

120546 --> 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:[~2022-12-12 11:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221208033127.57161-1-jingjing.wu@intel.com>
2022-12-08  3:33 ` checkpatch
2022-12-08  5:04 ` 0-day Robot
2022-12-08 16:05 ` qemudev
2022-12-08 16:06 ` qemudev
2022-12-08 16:41 ` qemudev [this message]
2022-12-08 16:42 ` qemudev
2022-12-10  0:30 ` qemudev
2022-12-10  0:31 ` qemudev
2022-12-08  5:33 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-08  5:18 dpdklab
2022-12-08  5:17 dpdklab
2022-12-08  5:09 dpdklab
2022-12-08  5:09 dpdklab
2022-12-08  5:08 dpdklab
2022-12-08  5:07 dpdklab
2022-12-08  5:06 dpdklab
2022-12-08  5:06 dpdklab
2022-12-08  5:06 dpdklab
2022-12-08  4:16 dpdklab
2022-12-08  4:06 dpdklab
2022-12-08  4:01 dpdklab
2022-12-08  4:01 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=202212081641.2B8GfkSJ197648@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).