From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151558-151568 [RFC 11/11] regexdev: remove unnecessary deref of function pointers
Date: Tue, 18 Feb 2025 02:33:30 +0800 [thread overview]
Message-ID: <202502171833.51HIXUT23317774@localhost.localdomain> (raw)
In-Reply-To: <20250217185743.169778-12-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/151568
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 17 Feb 2025 10:54:00 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e5176f23ae8b31437c3e5eb875c81f95bf3a9942
151558-151568 --> 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:[~2025-02-17 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250217185743.169778-12-stephen@networkplumber.org>
2025-02-17 18:33 ` qemudev [this message]
2025-02-17 18:37 ` qemudev
2025-02-17 18:59 ` |SUCCESS| pw151568 " checkpatch
2025-02-17 19:49 ` |PENDING| pw151558-151568 [PATCH] [RFC,11/11] regexdev: remove unnec dpdklab
2025-02-17 19:54 ` dpdklab
2025-02-17 19:57 ` |SUCCESS| " dpdklab
2025-02-17 20:00 ` dpdklab
2025-02-17 20:03 ` |SUCCESS| pw151568 [RFC 11/11] regexdev: remove unnecessary deref of function pointers 0-day Robot
2025-02-17 20:06 ` |PENDING| pw151558-151568 [PATCH] [RFC,11/11] regexdev: remove unnec dpdklab
2025-02-17 20:06 ` |SUCCESS| " dpdklab
2025-02-17 20:20 ` dpdklab
2025-02-17 20:22 ` dpdklab
2025-02-17 20:24 ` dpdklab
2025-02-17 20:25 ` dpdklab
2025-02-17 20:43 ` dpdklab
2025-02-17 21:02 ` dpdklab
2025-02-17 21:39 ` dpdklab
2025-02-17 22:25 ` dpdklab
2025-02-17 22:57 ` dpdklab
2025-02-19 4:25 ` 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=202502171833.51HIXUT23317774@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).