automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124573 [PATCH v1] ethdev: remove bitfields from trace
Date: Wed, 1 Mar 2023 16:14:55 +0800	[thread overview]
Message-ID: <202303010814.3218EtAs952133@localhost.localdomain> (raw)
In-Reply-To: <20230228155516.2403535-1-adwivedi@marvell.com>

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

_Compilation OK_

Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Tue, 28 Feb 2023 21:25:16 +0530
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: f09877166b29c89e8a602e0fd5b1289b26a88e8c

124573 --> 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:[~2023-03-01  8:29 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230228155516.2403535-1-adwivedi@marvell.com>
2023-02-28 15:56 ` checkpatch
2023-02-28 17:39 ` 0-day Robot
2023-03-01  8:14 ` qemudev [this message]
2023-03-01  8:15 ` qemudev
2023-02-28 21:45 |SUCCESS| pw124573 [PATCH] [v1] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-28 21:45 dpdklab
2023-02-28 21:32 dpdklab
2023-02-28 21:31 dpdklab
2023-02-28 21:27 dpdklab
2023-02-28 21:15 dpdklab
2023-02-28 21:11 dpdklab
2023-02-28 21:11 dpdklab
2023-02-28 21:07 dpdklab
2023-02-28 21:07 dpdklab
2023-02-28 20:58 dpdklab
2023-02-28 20:56 dpdklab
2023-02-28 20:36 dpdklab
2023-02-28 20:32 dpdklab
2023-02-28 20:08 dpdklab
2023-02-28 20:05 dpdklab
2023-02-28 19:07 dpdklab
2023-02-28 18:12 dpdklab
2023-02-28 18:12 dpdklab
2023-02-28 18:09 dpdklab
2023-02-28 18:02 dpdklab
2023-02-28 18:00 dpdklab
2023-02-28 17:58 dpdklab
2023-02-28 17:57 dpdklab
2023-02-28 17:55 dpdklab
2023-02-28 17:48 dpdklab
2023-02-28 17:47 dpdklab
2023-02-28 17:45 dpdklab
2023-02-28 17:39 dpdklab
2023-02-28 17:38 dpdklab
2023-02-28 17:34 dpdklab
2023-02-28 17:26 dpdklab
2023-02-28 17:17 dpdklab
2023-02-28 17:15 dpdklab
2023-02-28 17:02 dpdklab
2023-02-28 16:40 dpdklab
2023-02-28 16:36 dpdklab
2023-02-28 16:33 dpdklab
2023-02-28 16:33 dpdklab
2023-02-28 16:31 dpdklab
2023-02-28 16:27 dpdklab
2023-02-28 16:26 dpdklab
2023-02-28 16:25 dpdklab
2023-02-28 16:24 dpdklab
2023-02-28 16:20 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=202303010814.3218EtAs952133@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).