From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124678-124684 [PATCH 9/9] raw/skeleton: fix segment fault when parse devargs
Date: Mon, 6 Mar 2023 15:25:41 +0800 [thread overview]
Message-ID: <202303060725.3267PfPU3958605@localhost.localdomain> (raw)
In-Reply-To: <20230302075012.32423-10-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124684
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 2 Mar 2023 07:50:04 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124678-124684 --> 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 prev parent reply other threads:[~2023-03-06 7:39 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302075012.32423-10-fengchengwen@huawei.com>
2023-03-02 7:57 ` |SUCCESS| pw124684 " checkpatch
2023-03-02 9:59 ` 0-day Robot
2023-03-06 7:25 ` qemudev [this message]
2023-03-06 7:26 ` |SUCCESS| pw124678-124684 " qemudev
2023-03-04 13:58 |SUCCESS| pw124678-124684 [PATCH] [9/9] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 13:34 dpdklab
2023-03-04 13:26 dpdklab
2023-03-04 13:24 dpdklab
2023-03-04 13:15 dpdklab
2023-03-04 13:11 dpdklab
2023-03-04 13:07 dpdklab
2023-03-04 13:07 dpdklab
2023-03-04 13:05 dpdklab
2023-03-04 13:04 dpdklab
2023-03-04 13:02 dpdklab
2023-03-04 13:02 dpdklab
2023-03-04 12:59 dpdklab
2023-03-04 12:59 dpdklab
2023-03-04 12:58 dpdklab
2023-03-04 12:15 dpdklab
2023-03-04 12:14 dpdklab
2023-03-04 12:12 dpdklab
2023-03-04 12:10 dpdklab
2023-03-04 12:08 dpdklab
2023-03-04 12:06 dpdklab
2023-03-04 12:05 dpdklab
2023-03-04 12:03 dpdklab
2023-03-04 11:57 dpdklab
2023-03-04 11:55 dpdklab
2023-03-04 11:45 dpdklab
2023-03-04 11:40 dpdklab
2023-03-03 11:15 dpdklab
2023-03-03 10:29 dpdklab
2023-03-03 3:32 dpdklab
2023-03-03 3:26 dpdklab
2023-03-02 18:34 dpdklab
2023-03-02 17:51 dpdklab
2023-03-02 17:45 dpdklab
2023-03-02 17:39 dpdklab
2023-03-02 17:38 dpdklab
2023-03-02 17:37 dpdklab
2023-03-02 17:35 dpdklab
2023-03-02 17:33 dpdklab
2023-03-02 17:31 dpdklab
2023-03-02 17:31 dpdklab
2023-03-02 17:30 dpdklab
2023-03-02 17:29 dpdklab
2023-03-02 17:28 dpdklab
2023-03-02 17:19 dpdklab
2023-03-02 17:18 dpdklab
2023-03-02 17:11 dpdklab
2023-03-02 17:07 dpdklab
2023-03-02 16:59 dpdklab
2023-03-02 16:54 dpdklab
2023-03-02 16:53 dpdklab
2023-03-02 16:52 dpdklab
2023-03-02 16:48 dpdklab
2023-03-02 16:44 dpdklab
2023-03-02 16:43 dpdklab
2023-03-02 16:42 dpdklab
2023-03-02 16:41 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=202303060725.3267PfPU3958605@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).