From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw157561 [PATCH v3 5/5] net/dpaa: fix resource leak coverity issue
Date: Tue, 14 Oct 2025 07:19:47 -0400 [thread overview]
Message-ID: <20251014111947.1910471-1-robot@bytheb.org> (raw)
In-Reply-To: <20251014101716.2885563-6-g.singh@nxp.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/157561/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18493919753
next prev parent reply other threads:[~2025-10-14 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251014101716.2885563-6-g.singh@nxp.com>
2025-10-14 9:44 ` |SUCCESS| pw157557-157561 " qemudev
2025-10-14 9:49 ` qemudev
2025-10-14 10:18 ` |SUCCESS| pw157561 " checkpatch
2025-10-14 10:45 ` |PENDING| pw157557-157561 [PATCH] [v3,5/5] net/dpaa: fix resource le dpdklab
2025-10-14 10:48 ` |SUCCESS| " dpdklab
2025-10-14 10:53 ` dpdklab
2025-10-14 10:56 ` |PENDING| " dpdklab
2025-10-14 10:56 ` |SUCCESS| " dpdklab
2025-10-14 10:58 ` |PENDING| " dpdklab
2025-10-14 11:09 ` |SUCCESS| " dpdklab
2025-10-14 11:19 ` 0-day Robot [this message]
2025-10-14 11:19 ` |SUCCESS| pw157561 [PATCH v3 5/5] net/dpaa: fix resource leak coverity issue 0-day Robot
2025-10-14 11:37 ` |SUCCESS| pw157557-157561 [PATCH] [v3,5/5] net/dpaa: fix resource le dpdklab
2025-10-14 11:49 ` dpdklab
2025-10-14 11:50 ` dpdklab
2025-10-14 12:35 ` dpdklab
2025-10-14 12:37 ` dpdklab
2025-10-14 13:30 ` dpdklab
2025-10-14 13:41 ` dpdklab
2025-10-14 13:54 ` dpdklab
2025-10-14 14:30 ` dpdklab
2025-10-14 14:53 ` dpdklab
2025-10-14 17:01 ` dpdklab
2025-10-14 17:01 ` dpdklab
2025-10-14 17:29 ` dpdklab
2025-10-14 17:38 ` 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=20251014111947.1910471-1-robot@bytheb.org \
--to=robot@bytheb.org \
--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).