From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158080 [PATCH v1 2/2] bus/cdx: fix incorrect device release on error
Date: Fri, 24 Oct 2025 07:00:52 -0400 [thread overview]
Message-ID: <20251024110052.3602069-1-robot@bytheb.org> (raw)
In-Reply-To: <05ecc81aefbbe2073416c0e78aed926ec9ad54b5.1761299581.git.anatoly.burakov@intel.com>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158080/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/236
next prev parent reply other threads:[~2025-10-24 11:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05ecc81aefbbe2073416c0e78aed926ec9ad54b5.1761299581.git.anatoly.burakov@intel.com>
2025-10-24 9:19 ` |SUCCESS| pw158079-158080 " qemudev
2025-10-24 9:24 ` qemudev
2025-10-24 9:53 ` |SUCCESS| pw158080 " checkpatch
2025-10-24 10:18 ` |PENDING| pw158079-158080 [PATCH] [v1,2/2] bus/cdx: fix incorrect de dpdklab
2025-10-24 10:21 ` dpdklab
2025-10-24 10:23 ` |SUCCESS| " dpdklab
2025-10-24 10:27 ` dpdklab
2025-10-24 10:30 ` |WARNING| " dpdklab
2025-10-24 10:31 ` |PENDING| " dpdklab
2025-10-24 10:31 ` |WARNING| " dpdklab
2025-10-24 10:39 ` |SUCCESS| " dpdklab
2025-10-24 10:42 ` dpdklab
2025-10-24 10:42 ` dpdklab
2025-10-24 10:44 ` dpdklab
2025-10-24 10:44 ` dpdklab
2025-10-24 10:48 ` dpdklab
2025-10-24 10:55 ` dpdklab
2025-10-24 11:00 ` |SUCCESS| pw158080 [PATCH v1 2/2] bus/cdx: fix incorrect device release on error 0-day Robot
2025-10-24 11:00 ` 0-day Robot [this message]
2025-10-24 11:08 ` |WARNING| pw158079-158080 [PATCH] [v1,2/2] bus/cdx: fix incorrect de dpdklab
2025-10-24 11:14 ` |SUCCESS| " dpdklab
2025-10-25 10:01 ` |PENDING| " dpdklab
2025-10-25 10:47 ` |WARNING| " dpdklab
2025-10-25 11:29 ` dpdklab
2025-10-25 18:16 ` |SUCCESS| " 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=20251024110052.3602069-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).