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| pw137342 [PATCH 3/3] net/nfp: add force reload firmware option
Date: Tue, 27 Feb 2024 07:05:07 -0500	[thread overview]
Message-ID: <20240227120507.1278032-1-robot@bytheb.org> (raw)
In-Reply-To: <20240227111551.3773862-4-chaoyong.he@corigine.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-02-27 12:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227111551.3773862-4-chaoyong.he@corigine.com>
2024-02-27 10:53 ` |SUCCESS| pw137340-137342 " qemudev
2024-02-27 10:58 ` qemudev
2024-02-27 11:18 ` |SUCCESS| pw137342 " checkpatch
2024-02-27 12:05 ` 0-day Robot [this message]
2024-02-27 19:45 ` |SUCCESS| pw137340-137342 [PATCH] [3/3] net/nfp: add force reload fi dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:04 ` |FAILURE| " dpdklab
2024-02-27 20:23 ` |SUCCESS| " dpdklab
2024-02-27 20:35 ` dpdklab
2024-02-27 20:37 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:46 ` dpdklab
2024-02-27 20:48 ` dpdklab
2024-02-27 22:53 ` dpdklab
2024-02-27 23:50 ` |FAILURE| " dpdklab
2024-02-28  6:54 ` |SUCCESS| " dpdklab
2024-02-28  6:58 ` dpdklab
2024-02-28  8:03 ` dpdklab
2024-02-28 16:00 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:38 ` 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=20240227120507.1278032-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).