From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw128667 [PATCH] bus/cdx: Fix resource leak
Date: Wed, 14 Jun 2023 18:17:28 +0800 [thread overview]
Message-ID: <202306141017.35EAHSI42685196@localhost.localdomain> (raw)
In-Reply-To: <20230614102424.224679-1-abhijit.gangurde@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/128667
_Compilation OK_
Submitter: Abhijit Gangurde <abhijit.gangurde@amd.com>
Date: Wed, 14 Jun 2023 15:54:24 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 050de60d8a5cef8b7c10b4471905ca8bf69d670e
128667 --> 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-06-14 10:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614102424.224679-1-abhijit.gangurde@amd.com>
2023-06-14 10:17 ` qemudev [this message]
2023-06-14 10:21 ` qemudev
2023-06-14 10:25 ` checkpatch
2023-06-14 11:59 ` 0-day Robot
2023-06-14 14:45 dpdklab
2023-06-14 14:50 dpdklab
2023-06-14 14:52 dpdklab
2023-06-14 14:53 dpdklab
2023-06-14 15:07 dpdklab
2023-06-14 15:08 dpdklab
2023-06-14 15:27 dpdklab
2023-06-14 15:28 dpdklab
2023-06-14 15:29 dpdklab
2023-06-14 15:36 dpdklab
2023-06-14 15:41 dpdklab
2023-06-14 15:41 dpdklab
2023-06-14 15:45 dpdklab
2023-06-14 15:45 dpdklab
2023-06-14 16:00 dpdklab
2023-06-14 16:00 dpdklab
2023-06-14 16:07 dpdklab
2023-06-14 16:23 dpdklab
2023-06-14 16:27 dpdklab
2023-06-14 16:57 dpdklab
2023-06-14 17:14 dpdklab
2023-06-14 17:14 dpdklab
2023-06-14 17:57 dpdklab
2023-06-14 19:21 dpdklab
2023-06-14 20:08 dpdklab
2023-06-14 20:28 dpdklab
2023-06-15 12:02 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=202306141017.35EAHSI42685196@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).