From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144889 [PATCH] net/gve: fix mbuf allocation memory leak for DQ Rx
Date: Wed, 2 Oct 2024 07:33:15 +0800 [thread overview]
Message-ID: <202410012333.491NXFFm2206228@localhost.localdomain> (raw)
In-Reply-To: <20241001234852.3312594-1-joshwash@google.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144889
_Compilation OK_
Submitter: Joshua Washington <joshwash@google.com>
Date: Tue, 1 Oct 2024 16:48:52 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 9456ac767bb1c2aa2a8de460ebe7318105ce2135
144889 --> 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-10-02 0:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241001234852.3312594-1-joshwash@google.com>
2024-10-01 23:33 ` qemudev [this message]
2024-10-01 23:37 ` qemudev
2024-10-01 23:49 ` checkpatch
2024-10-02 0:44 ` 0-day Robot
2024-10-02 2:11 ` |PENDING| pw144889 [PATCH] net/gve: fix mbuf allocation memory leak dpdklab
2024-10-02 2:18 ` |SUCCESS| " dpdklab
2024-10-02 2:25 ` dpdklab
2024-10-02 2:26 ` dpdklab
2024-10-02 2:26 ` dpdklab
2024-10-02 2:26 ` |PENDING| " dpdklab
2024-10-02 2:27 ` |SUCCESS| " dpdklab
2024-10-02 2:30 ` dpdklab
2024-10-02 2:37 ` dpdklab
2024-10-02 2:45 ` dpdklab
2024-10-02 2:55 ` |PENDING| " dpdklab
2024-10-02 3:07 ` |SUCCESS| " dpdklab
2024-10-02 4:27 ` dpdklab
2024-10-02 5:09 ` dpdklab
2024-10-02 5:13 ` dpdklab
2024-10-02 5:38 ` dpdklab
2024-10-02 6:20 ` dpdklab
2024-10-02 9:48 ` |PENDING| " dpdklab
2024-10-02 10:09 ` |SUCCESS| " dpdklab
2024-10-02 10:10 ` dpdklab
2024-10-02 10:59 ` dpdklab
2024-10-02 12:49 ` dpdklab
2024-10-02 13:11 ` 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=202410012333.491NXFFm2206228@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).