From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125153-125169 [PATCH v2 16/16] rcu: use previous value atomic fetch operations
Date: Thu, 16 Mar 2023 05:06:44 +0800 [thread overview]
Message-ID: <202303152106.32FL6iPi3794520@localhost.localdomain> (raw)
In-Reply-To: <1678914945-10638-17-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125169
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 15 Mar 2023 14:15:30 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8c9bfcb1553d756eb5392a56ac7813b3865c3ec7
125153-125169 --> 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
next parent reply other threads:[~2023-03-15 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1678914945-10638-17-git-send-email-roretzla@linux.microsoft.com>
2023-03-15 21:06 ` qemudev [this message]
2023-03-15 21:10 ` qemudev
2023-03-15 21:19 ` |SUCCESS| pw125169 " checkpatch
2023-03-15 23:59 ` 0-day Robot
2023-03-18 3:42 |SUCCESS| pw125153-125169 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 23:13 dpdklab
2023-03-15 22:48 dpdklab
2023-03-15 22:28 dpdklab
2023-03-15 22:11 dpdklab
2023-03-15 22:07 dpdklab
2023-03-15 22:05 dpdklab
2023-03-15 22:01 dpdklab
2023-03-15 21:58 dpdklab
2023-03-15 21:56 dpdklab
2023-03-15 21:52 dpdklab
2023-03-15 21:52 dpdklab
2023-03-15 21:51 dpdklab
2023-03-15 21:51 dpdklab
2023-03-15 21:50 dpdklab
2023-03-15 21:45 dpdklab
2023-03-15 21:45 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=202303152106.32FL6iPi3794520@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).