automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125017-125032 [PATCH 16/16] rcu: use previous value atomic fetch operations
Date: Sat, 11 Mar 2023 06:07:01 +0800	[thread overview]
Message-ID: <202303102207.32AM71SE3717603@localhost.localdomain> (raw)
In-Reply-To: <1678486530-20688-17-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Fri, 10 Mar 2023 14:15:15 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: b15d75b2872efce397d827dac78692a919358302

125017-125032 --> 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-03-10 22:20 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1678486530-20688-17-git-send-email-roretzla@linux.microsoft.com>
2023-03-10 22:07 ` qemudev [this message]
2023-03-10 22:10 ` qemudev
2023-03-10 22:18 ` |SUCCESS| pw125032 " checkpatch
2023-03-11  0:52 ` 0-day Robot
2023-03-10 23:55 |SUCCESS| pw125017-125032 [PATCH] [16/16] " dpdklab
2023-03-11  0:03 dpdklab
2023-03-11  0:08 dpdklab
2023-03-11  0:16 dpdklab
2023-03-11  0:16 dpdklab
2023-03-11  0:17 dpdklab
2023-03-11  0:26 dpdklab
2023-03-11  0:27 dpdklab
2023-03-11  0:28 dpdklab
2023-03-11  0:29 dpdklab
2023-03-11  0:33 dpdklab
2023-03-11  0:34 dpdklab
2023-03-11  0:35 dpdklab
2023-03-11  0:39 dpdklab
2023-03-11  0:42 dpdklab
2023-03-11  0:42 dpdklab
2023-03-11  0:43 dpdklab
2023-03-11  0:44 dpdklab
2023-03-11  0:48 dpdklab
2023-03-11  0:57 dpdklab
2023-03-11  0:59 dpdklab
2023-03-11  0:59 dpdklab
2023-03-11  1:03 dpdklab
2023-03-11  1:08 dpdklab
2023-03-11  1:09 dpdklab
2023-03-11  1:11 dpdklab
2023-03-11  1:15 dpdklab
2023-03-11  1:30 dpdklab
2023-03-11 16:31 dpdklab
2023-03-11 17:53 dpdklab
2023-03-11 18:56 dpdklab
2023-03-11 19:19 dpdklab
2023-03-12  6:24 dpdklab
2023-03-12  6:26 dpdklab
2023-03-12  6:31 dpdklab
2023-03-12  6:33 dpdklab
2023-03-12  6:35 dpdklab
2023-03-12  6:39 dpdklab
2023-03-12  6:49 dpdklab
2023-03-12  6:52 dpdklab
2023-03-12  6:56 dpdklab
2023-03-12  7:10 dpdklab
2023-03-12  7:12 dpdklab
2023-03-12  7:18 dpdklab
2023-03-12  7:19 dpdklab
2023-03-12  7:24 dpdklab
2023-03-12  7:25 dpdklab
2023-03-12  7:26 dpdklab
2023-03-12  7:28 dpdklab
2023-03-12  7:32 dpdklab
2023-03-12  7:32 dpdklab
2023-03-12  7:35 dpdklab
2023-03-12  7:35 dpdklab
2023-03-12  7:37 dpdklab
2023-03-12  7:40 dpdklab
2023-03-12  7:41 dpdklab
2023-03-12  7:48 dpdklab
2023-03-12  7:50 dpdklab
2023-03-12  8:24 dpdklab
2023-03-12  8:25 dpdklab
2023-03-12 16:49 dpdklab
2023-03-12 18:38 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=202303102207.32AM71SE3717603@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).