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| pw154475 [PATCH v2] dts: fix devbind initialization bug
Date: Mon, 16 Jun 2025 15:47:33 -0400	[thread overview]
Message-ID: <20250616194733.588507-1-robot@bytheb.org> (raw)
In-Reply-To: <20250616183859.646384-1-dmarx@iol.unh.edu>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/154475/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15689329841

  parent reply	other threads:[~2025-06-16 19:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250616183859.646384-1-dmarx@iol.unh.edu>
2025-06-16 18:07 ` qemudev
2025-06-16 18:11 ` qemudev
2025-06-16 18:38 ` checkpatch
2025-06-16 19:10 ` |SUCCESS| pw154475 [PATCH] [v2] " dpdklab
2025-06-16 19:24 ` dpdklab
2025-06-16 19:25 ` dpdklab
2025-06-16 19:36 ` |FAILURE| " dpdklab
2025-06-16 19:38 ` |SUCCESS| " dpdklab
2025-06-16 19:43 ` |PENDING| " dpdklab
2025-06-16 19:47 ` 0-day Robot [this message]
2025-06-16 19:53 ` dpdklab
2025-06-16 19:59 ` |SUCCESS| " dpdklab
2025-06-16 20:00 ` |PENDING| " dpdklab
2025-06-16 20:11 ` |FAILURE| " dpdklab
2025-06-16 20:37 ` |SUCCESS| " dpdklab
2025-06-16 20:38 ` dpdklab
2025-06-16 20:42 ` |FAILURE| " dpdklab
2025-06-16 20:42 ` dpdklab
2025-06-16 20:52 ` dpdklab
2025-06-16 20:53 ` dpdklab
2025-06-16 21:52 ` |SUCCESS| " dpdklab
2025-06-17  0:29 ` dpdklab
2025-06-17  0:31 ` dpdklab
2025-06-17  0:35 ` dpdklab
2025-06-17  0:38 ` dpdklab
2025-06-17  0:41 ` dpdklab
2025-06-17  0:50 ` dpdklab
2025-06-17  0:53 ` dpdklab
2025-06-17  0:57 ` dpdklab
2025-06-17  1:13 ` dpdklab
2025-06-17  2:22 ` 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=20250616194733.588507-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).