From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158192 [PATCH v10 3/3] doc: note on unsupported completion queue sharing
Date: Tue, 28 Oct 2025 11:40:02 -0400 [thread overview]
Message-ID: <20251028154002.1559645-1-robot@bytheb.org> (raw)
In-Reply-To: <20251028142202.137392-4-shaiq.wani@intel.com>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158192/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/263
next prev parent reply other threads:[~2025-10-28 15:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251028142202.137392-4-shaiq.wani@intel.com>
2025-10-28 13:47 ` |SUCCESS| pw158190-158192 " qemudev
2025-10-28 13:52 ` qemudev
2025-10-28 14:22 ` |SUCCESS| pw158192 " checkpatch
2025-10-28 15:09 ` |PENDING| pw158190-158192 [PATCH] [v10,3/3] doc: note on unsupported dpdklab
2025-10-28 15:11 ` |SUCCESS| " dpdklab
2025-10-28 15:16 ` dpdklab
2025-10-28 15:18 ` dpdklab
2025-10-28 15:20 ` dpdklab
2025-10-28 15:30 ` dpdklab
2025-10-28 15:35 ` dpdklab
2025-10-28 15:39 ` |SUCCESS| pw158192 [PATCH v10 3/3] doc: note on unsupported completion queue sharing 0-day Robot
2025-10-28 15:40 ` 0-day Robot [this message]
2025-10-28 16:07 ` |SUCCESS| pw158190-158192 [PATCH] [v10,3/3] doc: note on unsupported dpdklab
2025-10-28 16:07 ` dpdklab
2025-10-28 16:11 ` |PENDING| " dpdklab
2025-10-28 19:58 ` |WARNING| " dpdklab
2025-10-28 20:10 ` |PENDING| " dpdklab
2025-10-28 20:45 ` |WARNING| " dpdklab
2025-10-28 21:12 ` |SUCCESS| " dpdklab
2025-10-28 21:40 ` dpdklab
2025-10-28 21:59 ` dpdklab
2025-10-28 22:00 ` dpdklab
2025-10-28 22:07 ` dpdklab
2025-10-28 23:05 ` |WARNING| " dpdklab
2025-10-28 23:06 ` dpdklab
2025-10-29 3:52 ` |SUCCESS| " dpdklab
2025-10-29 8:36 ` 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=20251028154002.1559645-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).