automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121377 [PATCH v7] doc: add PMD known issue
Date: Tue, 27 Dec 2022 09:18:36 +0800	[thread overview]
Message-ID: <202212270118.2BR1Ia9u068611@localhost.localdomain> (raw)
In-Reply-To: <20221226025244.18972-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Mon, 26 Dec 2022 10:52:44 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 43d326b6f923f32473f550228910e1bd5de3f3fb

121377 --> 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-27  1:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221226025244.18972-1-mingjinx.ye@intel.com>
2022-12-26  2:47 ` qemudev
2022-12-26  2:51 ` |FAILURE| " qemudev
2022-12-26  2:55 ` |SUCCESS| " checkpatch
2022-12-26  3:39 ` |FAILURE| " 0-day Robot
2022-12-27  1:18 ` qemudev [this message]
2022-12-27  1:22 ` |SUCCESS| " qemudev
2022-12-26  3:20 |SUCCESS| pw121377 [PATCH] [v7] " dpdklab
2022-12-26  3:24 dpdklab
2022-12-26  3:28 dpdklab
2022-12-26  3:32 dpdklab
2022-12-26  3:40 dpdklab
2022-12-26  3:44 dpdklab
2022-12-26  3:57 dpdklab
2022-12-26  4:21 dpdklab
2022-12-26  4:22 dpdklab
2022-12-26  4:27 dpdklab
2022-12-26  4:28 dpdklab
2022-12-26  4:28 dpdklab
2022-12-26  4:33 dpdklab
2022-12-26  4:35 dpdklab
2022-12-26  4:47 dpdklab
2022-12-26  4:51 dpdklab
2022-12-26  4:54 dpdklab
2022-12-26  5:04 dpdklab
2022-12-26  5:06 dpdklab
2022-12-26  5:08 dpdklab
2022-12-26  5:10 dpdklab
2022-12-26  5:11 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=202212270118.2BR1Ia9u068611@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).