From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147185-147190 [PATCH v2 6/6] drivers: use bitops API instead of compiler builtins
Date: Fri, 25 Oct 2024 14:45:26 +0800 [thread overview]
Message-ID: <202410250645.49P6jQ5X3434219@localhost.localdomain> (raw)
In-Reply-To: <20241025070424.3916007-7-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147190
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri, 25 Oct 2024 09:04:18 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 90cb8ff8196f9b9c1c2bcee1c94ea583789bb63f
147185-147190 --> 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-10-25 7:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241025070424.3916007-7-david.marchand@redhat.com>
2024-10-25 6:45 ` qemudev [this message]
2024-10-25 6:49 ` qemudev
2024-10-25 7:05 ` |SUCCESS| pw147190 " checkpatch
2024-10-25 8:07 ` 0-day Robot
2024-10-25 15:28 ` |SUCCESS| pw147185-147190 [PATCH] [v2,6/6] drivers: use bitops API i dpdklab
2024-10-25 15:50 ` dpdklab
2024-10-25 15:59 ` dpdklab
2024-10-26 4:20 ` dpdklab
2024-10-26 5:22 ` dpdklab
2024-10-26 17:12 ` dpdklab
2024-10-27 9:44 ` |PENDING| " dpdklab
2024-10-27 17:12 ` |SUCCESS| " dpdklab
2024-10-27 17:25 ` dpdklab
2024-10-28 10:04 ` |PENDING| " dpdklab
2024-10-28 11:58 ` |WARNING| " dpdklab
2024-10-28 15:51 ` dpdklab
2024-10-29 6:14 ` |PENDING| " dpdklab
2024-10-29 8:35 ` |SUCCESS| " dpdklab
2024-10-29 8:42 ` dpdklab
2024-11-01 19:43 ` dpdklab
2024-11-02 1:46 ` 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=202410250645.49P6jQ5X3434219@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).