automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158107 [PATCH v5 8/8] doc: update documentation on pdump library
Date: Fri, 24 Oct 2025 20:22:31 -0400	[thread overview]
Message-ID: <20251025002231.1115535-1-robot@bytheb.org> (raw)
In-Reply-To: <20251024215456.282171-9-stephen@networkplumber.org>

From: robot@bytheb.org

Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158107/

_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/241

  parent reply	other threads:[~2025-10-25  0:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251024215456.282171-9-stephen@networkplumber.org>
2025-10-24 21:21 ` |SUCCESS| pw158100-158107 " qemudev
2025-10-24 21:26 ` qemudev
2025-10-24 21:56 ` |SUCCESS| pw158107 " checkpatch
2025-10-24 22:24 ` |PENDING| pw158100-158107 [PATCH] [v5,8/8] doc: update documentation dpdklab
2025-10-24 22:25 ` |SUCCESS| " dpdklab
2025-10-24 22:30 ` dpdklab
2025-10-24 22:32 ` |PENDING| " dpdklab
2025-10-24 22:35 ` |WARNING| " dpdklab
2025-10-24 22:36 ` dpdklab
2025-10-24 22:41 ` |SUCCESS| " dpdklab
2025-10-24 22:42 ` dpdklab
2025-10-24 22:47 ` dpdklab
2025-10-24 23:00 ` |PENDING| " dpdklab
2025-10-24 23:27 ` |SUCCESS| " dpdklab
2025-10-24 23:36 ` |WARNING| " dpdklab
2025-10-25  0:00 ` |SUCCESS| " dpdklab
2025-10-25  0:12 ` dpdklab
2025-10-25  0:12 ` dpdklab
2025-10-25  0:19 ` dpdklab
2025-10-25  0:22 ` |SUCCESS| pw158107 [PATCH v5 8/8] doc: update documentation on pdump library 0-day Robot
2025-10-25  0:22 ` 0-day Robot [this message]
2025-10-25  1:30 ` |SUCCESS| pw158100-158107 [PATCH] [v5,8/8] doc: update documentation dpdklab
2025-10-25 21:35 ` |WARNING| " dpdklab
2025-10-25 21:41 ` |PENDING| " dpdklab
2025-10-25 22:02 ` |WARNING| " dpdklab
2025-10-26  4:59 ` |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=20251025002231.1115535-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).