From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw157805 [PATCH dpdk] net/tap: fix interrupt callback crash after failed start
Date: Fri, 17 Oct 2025 09:35:37 -0400 [thread overview]
Message-ID: <20251017133537.800482-1-robot@bytheb.org> (raw)
In-Reply-To: <20251017121946.421658-2-rjarry@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/157805/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/206
next prev parent reply other threads:[~2025-10-17 13:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251017121946.421658-2-rjarry@redhat.com>
2025-10-17 11:45 ` qemudev
2025-10-17 11:50 ` qemudev
2025-10-17 12:19 ` checkpatch
2025-10-17 12:45 ` |PENDING| pw157805 [PATCH] net/tap: fix interrupt callback crash aft dpdklab
2025-10-17 12:46 ` |SUCCESS| " dpdklab
2025-10-17 12:47 ` dpdklab
2025-10-17 12:50 ` dpdklab
2025-10-17 12:54 ` dpdklab
2025-10-17 13:03 ` |FAILURE| " dpdklab
2025-10-17 13:05 ` |SUCCESS| " dpdklab
2025-10-17 13:08 ` |FAILURE| " dpdklab
2025-10-17 13:15 ` |PENDING| " dpdklab
2025-10-17 13:17 ` dpdklab
2025-10-17 13:26 ` |SUCCESS| " dpdklab
2025-10-17 13:35 ` |SUCCESS| pw157805 [PATCH dpdk] net/tap: fix interrupt callback crash after failed start 0-day Robot
2025-10-17 13:35 ` 0-day Robot [this message]
2025-10-17 13:39 ` |SUCCESS| pw157805 [PATCH] net/tap: fix interrupt callback crash aft dpdklab
2025-10-17 13:44 ` dpdklab
2025-10-17 13:59 ` dpdklab
2025-10-17 14:00 ` dpdklab
2025-10-17 15:06 ` dpdklab
2025-10-17 15:14 ` dpdklab
2025-10-17 15:24 ` dpdklab
2025-10-17 16:24 ` dpdklab
2025-10-17 16:47 ` |FAILURE| " dpdklab
2025-10-17 18:42 ` |PENDING| " dpdklab
2025-10-17 18:44 ` |WARNING| " dpdklab
2025-10-17 19:26 ` dpdklab
2025-10-17 23:18 ` |SUCCESS| " dpdklab
2025-10-18 5:55 ` 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=20251017133537.800482-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).