From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126698 [PATCH v3] ring: fix use after free in ring release
Date: Fri, 5 May 2023 14:37:53 +0800 [thread overview]
Message-ID: <202305050637.3456br4b527757@localhost.localdomain> (raw)
In-Reply-To: <21867862766caee191228a5fe438fde899e6fd7f.1683268586.git.wangyunjian@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126698
_Compilation OK_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Fri, 5 May 2023 14:48:34 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d03446724972d2a1bb645ce7f3e64f5ef0203d61
126698 --> 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-05-05 6:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <21867862766caee191228a5fe438fde899e6fd7f.1683268586.git.wangyunjian@huawei.com>
2023-05-05 6:37 ` qemudev [this message]
2023-05-05 6:41 ` qemudev
2023-05-05 6:50 ` checkpatch
2023-05-05 7:39 ` |SUCCESS| pw126698 [dpdk-dev] " 0-day Robot
2023-05-05 7:22 |SUCCESS| pw126698 [PATCH] [v3] " dpdklab
2023-05-05 7:24 dpdklab
2023-05-05 7:29 dpdklab
2023-05-05 7:30 dpdklab
2023-05-05 7:30 dpdklab
2023-05-05 7:31 dpdklab
2023-05-05 7:34 dpdklab
2023-05-05 7:36 dpdklab
2023-05-05 7:36 dpdklab
2023-05-05 7:39 dpdklab
2023-05-05 7:41 dpdklab
2023-05-05 7:44 dpdklab
2023-05-05 7:45 dpdklab
2023-05-05 7:49 dpdklab
2023-05-05 7:51 dpdklab
2023-05-05 7:54 dpdklab
2023-05-05 7:56 dpdklab
2023-05-05 7:56 dpdklab
2023-05-05 7:57 dpdklab
2023-05-05 7:58 dpdklab
2023-05-05 7:58 dpdklab
2023-05-05 7:58 dpdklab
2023-05-05 8:00 dpdklab
2023-05-05 8:02 dpdklab
2023-05-05 8:03 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=202305050637.3456br4b527757@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).