automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125329-125344 [PATCH v3 16/16] rcu: use previous value atomic fetch operations
Date: Tue, 21 Mar 2023 02:52:23 +0800	[thread overview]
Message-ID: <202303201852.32KIqNBp2907771@localhost.localdomain> (raw)
In-Reply-To: <1679338836-21321-17-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 20 Mar 2023 12:00:21 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 33949800f1afcb7527b6e36c60c1548687ccb673

125329-125344 --> 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-20 19:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1679338836-21321-17-git-send-email-roretzla@linux.microsoft.com>
2023-03-20 18:52 ` qemudev [this message]
2023-03-20 18:56 ` qemudev
2023-03-20 19:04 ` |SUCCESS| pw125344 " checkpatch
2023-03-20 21:39 ` 0-day Robot
2023-03-24  9:45 |SUCCESS| pw125329-125344 [PATCH] [v3, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24  9:43 dpdklab
2023-03-24  5:33 dpdklab
2023-03-24  5:32 dpdklab
2023-03-23 22:44 dpdklab
2023-03-23 15:21 dpdklab
2023-03-22  3:03 dpdklab
2023-03-22  1:16 dpdklab
2023-03-21 20:12 dpdklab
2023-03-21 20:07 dpdklab
2023-03-21 15:54 dpdklab
2023-03-21 13:06 dpdklab
2023-03-21 12:09 dpdklab
2023-03-21  9:03 dpdklab
2023-03-21  8:39 dpdklab
2023-03-21  8:36 dpdklab
2023-03-21  8:29 dpdklab
2023-03-21  8:27 dpdklab
2023-03-21  8:24 dpdklab
2023-03-21  8:23 dpdklab
2023-03-21  8:22 dpdklab
2023-03-21  8:20 dpdklab
2023-03-21  8:20 dpdklab
2023-03-21  8:14 dpdklab
2023-03-21  8:08 dpdklab
2023-03-21  0:56 dpdklab
2023-03-21  0:44 dpdklab
2023-03-20 22:37 dpdklab
2023-03-20 22:25 dpdklab
2023-03-20 22:25 dpdklab
2023-03-20 22:24 dpdklab
2023-03-20 22:19 dpdklab
2023-03-20 22:19 dpdklab
2023-03-20 22:15 dpdklab
2023-03-20 21:52 dpdklab
2023-03-20 21:47 dpdklab
2023-03-20 21:39 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=202303201852.32KIqNBp2907771@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).