From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151691-151705 [PATCH v9 15/15] devtools/cocci: add script to find problematic memset
Date: Fri, 21 Feb 2025 00:09:43 +0800 [thread overview]
Message-ID: <202502201609.51KG9hU11294299@localhost.localdomain> (raw)
In-Reply-To: <20250220164151.9606-16-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/151705
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 20 Feb 2025 08:27:07 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fab31a03ba98e7457284df95dd9eef2223a4ccaa
151691-151705 --> 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-20 16:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250220164151.9606-16-stephen@networkplumber.org>
2025-02-20 16:09 ` qemudev [this message]
2025-02-20 16:14 ` qemudev
2025-02-20 16:44 ` |SUCCESS| pw151705 " checkpatch
2025-02-20 17:44 ` 0-day Robot
2025-02-20 18:47 ` |SUCCESS| pw151691-151705 [PATCH] [v9,15/15] devtools/cocci: add scr dpdklab
2025-02-20 18:49 ` dpdklab
2025-02-20 19:03 ` |PENDING| " dpdklab
2025-02-20 19:05 ` |SUCCESS| " dpdklab
2025-02-20 19:08 ` dpdklab
2025-02-20 19:09 ` dpdklab
2025-02-20 19:28 ` |PENDING| " dpdklab
2025-02-20 19:37 ` |SUCCESS| " dpdklab
2025-02-20 19:45 ` dpdklab
2025-02-20 20:11 ` |PENDING| " dpdklab
2025-02-20 21:05 ` dpdklab
2025-02-21 0:38 ` |SUCCESS| " dpdklab
2025-02-21 4:20 ` 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=202502201609.51KG9hU11294299@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).