From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137401-137403 [PATCH 3/3] rcu: use rte macro instead of GCC attribute
Date: Wed, 28 Feb 2024 06:46:00 +0800 [thread overview]
Message-ID: <202402272246.41RMk08b435706@localhost.localdomain> (raw)
In-Reply-To: <1709075273-6885-4-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137403
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 27 Feb 2024 15:07:51 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137401-137403 --> 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:[~2024-02-27 23:10 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709075273-6885-4-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 22:46 ` qemudev [this message]
2024-02-27 22:50 ` qemudev
2024-02-27 23:09 ` |SUCCESS| pw137403 " checkpatch
2024-02-28 0:05 ` 0-day Robot
2024-02-28 0:32 ` |SUCCESS| pw137401-137403 [PATCH] [3/3] rcu: use rte macro instead o dpdklab
2024-02-28 0:32 ` dpdklab
2024-02-28 0:40 ` dpdklab
2024-02-28 0:46 ` dpdklab
2024-02-28 1:12 ` dpdklab
2024-02-28 1:16 ` dpdklab
2024-02-28 1:16 ` dpdklab
2024-02-28 1:18 ` dpdklab
2024-02-28 1:19 ` dpdklab
2024-02-28 1:19 ` dpdklab
2024-02-28 1:21 ` dpdklab
2024-02-28 1:22 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 2:10 ` dpdklab
2024-02-28 2:15 ` dpdklab
2024-02-28 2:16 ` dpdklab
2024-02-28 2:26 ` dpdklab
2024-02-28 2:26 ` dpdklab
2024-02-28 2:27 ` dpdklab
2024-02-28 2:27 ` dpdklab
2024-02-28 2:28 ` dpdklab
2024-02-28 2:28 ` dpdklab
2024-02-28 2:29 ` dpdklab
2024-02-28 2:30 ` dpdklab
2024-02-28 2:31 ` dpdklab
2024-02-28 2:31 ` dpdklab
2024-02-28 2:31 ` dpdklab
2024-02-28 2:43 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 2:55 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:58 ` dpdklab
2024-02-28 2:59 ` dpdklab
2024-02-28 3:00 ` dpdklab
2024-02-28 3:01 ` dpdklab
2024-02-28 3:01 ` dpdklab
2024-02-28 3:01 ` dpdklab
2024-02-28 3:03 ` dpdklab
2024-02-28 3:03 ` dpdklab
2024-02-28 3:12 ` dpdklab
2024-02-28 3:12 ` dpdklab
2024-02-28 3:15 ` dpdklab
2024-02-28 3:32 ` dpdklab
2024-02-28 3:39 ` dpdklab
2024-02-28 3:46 ` dpdklab
2024-02-28 3:49 ` dpdklab
2024-02-28 3:52 ` dpdklab
2024-02-28 3:56 ` dpdklab
2024-02-28 4:01 ` dpdklab
2024-02-28 4:01 ` dpdklab
2024-02-28 4:02 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:18 ` dpdklab
2024-02-28 4:21 ` dpdklab
2024-02-28 6:44 ` dpdklab
2024-02-28 9:33 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:34 ` dpdklab
2024-02-28 20:55 ` dpdklab
2024-02-29 12:42 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 15:48 ` dpdklab
2024-02-29 16:06 ` dpdklab
2024-02-29 16:11 ` 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=202402272246.41RMk08b435706@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).