From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138449-138454 [PATCH v4 6/6] argparse: fix doc don't display two hyphens
Date: Mon, 18 Mar 2024 18:58:58 +0800 [thread overview]
Message-ID: <202403181058.42IAwwkg2524379@localhost.localdomain> (raw)
In-Reply-To: <20240318111838.16991-7-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138454
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Mon, 18 Mar 2024 11:18:33 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138449-138454 --> 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-03-18 11:23 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318111838.16991-7-fengchengwen@huawei.com>
2024-03-18 10:58 ` qemudev [this message]
2024-03-18 11:03 ` qemudev
2024-03-18 11:22 ` |WARNING| pw138454 " checkpatch
2024-03-18 12:19 ` |SUCCESS| pw138449-138454 [PATCH] [v4,6/6] argparse: fix doc don't d dpdklab
2024-03-18 12:19 ` dpdklab
2024-03-18 12:20 ` dpdklab
2024-03-18 12:22 ` dpdklab
2024-03-18 12:22 ` dpdklab
2024-03-18 12:23 ` dpdklab
2024-03-18 12:23 ` |SUCCESS| pw138454 [PATCH v4 6/6] argparse: fix doc don't display two hyphens 0-day Robot
2024-03-18 12:23 ` |SUCCESS| pw138449-138454 [PATCH] [v4,6/6] argparse: fix doc don't d dpdklab
2024-03-18 12:23 ` dpdklab
2024-03-18 12:24 ` dpdklab
2024-03-18 12:24 ` dpdklab
2024-03-18 12:25 ` dpdklab
2024-03-18 12:25 ` dpdklab
2024-03-18 12:26 ` dpdklab
2024-03-18 12:26 ` dpdklab
2024-03-18 12:26 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:27 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:28 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:29 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:30 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:32 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:33 ` dpdklab
2024-03-18 12:36 ` dpdklab
2024-03-18 12:37 ` dpdklab
2024-03-18 12:38 ` dpdklab
2024-03-18 12:38 ` dpdklab
2024-03-18 12:40 ` dpdklab
2024-03-18 12:40 ` dpdklab
2024-03-18 12:43 ` dpdklab
2024-03-18 12:44 ` dpdklab
2024-03-18 12:52 ` dpdklab
2024-03-18 12:56 ` dpdklab
2024-03-18 13:36 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-20 14:30 ` dpdklab
2024-03-20 15:06 ` 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=202403181058.42IAwwkg2524379@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).