From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123157 [PATCH] app/testpmd: fix crash on cleanup
Date: Mon, 6 Feb 2023 23:38:47 +0800 [thread overview]
Message-ID: <202302061538.316FcloJ3367361@localhost.localdomain> (raw)
In-Reply-To: <20230206154946.750829-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123157
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 6 Feb 2023 16:49:46 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 74fce0da4e22931e6382d9345fb7e0ad360426f5
123157 --> 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:[~2023-02-06 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230206154946.750829-1-david.marchand@redhat.com>
2023-02-06 15:38 ` qemudev [this message]
2023-02-06 15:42 ` qemudev
2023-02-06 15:50 ` checkpatch
2023-02-06 16:41 ` |FAILURE| " 0-day Robot
2023-02-07 0:52 |SUCCESS| " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 0:14 dpdklab
2023-02-06 22:52 dpdklab
2023-02-06 21:32 dpdklab
2023-02-06 21:31 dpdklab
2023-02-06 21:31 dpdklab
2023-02-06 21:31 dpdklab
2023-02-06 20:32 dpdklab
2023-02-06 19:43 dpdklab
2023-02-06 17:14 dpdklab
2023-02-06 16:56 dpdklab
2023-02-06 16:54 dpdklab
2023-02-06 16:49 dpdklab
2023-02-06 16:44 dpdklab
2023-02-06 16:40 dpdklab
2023-02-06 16:37 dpdklab
2023-02-06 16:32 dpdklab
2023-02-06 16:27 dpdklab
2023-02-06 16:26 dpdklab
2023-02-06 16:21 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=202302061538.316FcloJ3367361@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).