automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126003-126020 [PATCH 18/18] common/idpf: update license and README
Date: Thu, 13 Apr 2023 17:42:57 +0800	[thread overview]
Message-ID: <202304130942.33D9gvT83067501@localhost.localdomain> (raw)
In-Reply-To: <20230413094502.1714755-19-wenjing.qiao@intel.com>

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

_Compilation OK_

Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Thu, 13 Apr 2023 05:44:45 -0400
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd

126003-126020 --> 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-04-13  9:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230413094502.1714755-19-wenjing.qiao@intel.com>
2023-04-13  9:42 ` qemudev [this message]
2023-04-13  9:46 ` qemudev
2023-04-13  9:54 ` |WARNING| pw126020 " checkpatch
2023-04-13 10:59 ` |SUCCESS| " 0-day Robot
2023-04-13 17:49 |SUCCESS| pw126003-126020 [PATCH] [18/18] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-04-13 14:54 dpdklab
2023-04-13 14:54 dpdklab
2023-04-13 14:53 dpdklab
2023-04-13 14:51 dpdklab
2023-04-13 14:50 dpdklab
2023-04-13 14:49 dpdklab
2023-04-13 14:49 dpdklab
2023-04-13 14:47 dpdklab
2023-04-13 14:45 dpdklab
2023-04-13 14:43 dpdklab
2023-04-13 14:26 dpdklab
2023-04-13 11:34 dpdklab
2023-04-13 11:20 dpdklab
2023-04-13 11:19 dpdklab
2023-04-13 11:11 dpdklab
2023-04-13 11:01 dpdklab
2023-04-13 10:56 dpdklab
2023-04-13 10:53 dpdklab
2023-04-13 10:53 dpdklab
2023-04-13 10:51 dpdklab
2023-04-13 10:51 dpdklab
2023-04-13 10:50 dpdklab
2023-04-13 10:49 dpdklab
2023-04-13 10:47 dpdklab
2023-04-13 10:47 dpdklab
2023-04-13 10:46 dpdklab
2023-04-13 10:44 dpdklab
2023-04-13 10:43 dpdklab
2023-04-13 10:39 dpdklab
2023-04-13 10:35 dpdklab
2023-04-13 10:35 dpdklab
2023-04-13 10:34 dpdklab
2023-04-13 10:31 dpdklab
2023-04-13 10:30 dpdklab
2023-04-13 10:30 dpdklab
2023-04-13 10:28 dpdklab
2023-04-13 10:28 dpdklab
2023-04-13 10:23 dpdklab
2023-04-13 10:21 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=202304130942.33D9gvT83067501@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).