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| pw124837 [PATCH] doc: fix naming of NVIDIA devices
Date: Tue,  7 Mar 2023 12:39:17 -0500	[thread overview]
Message-ID: <20230307173917.732461-1-robot@bytheb.org> (raw)
In-Reply-To: <20230307152825.263841-1-thomas@monjalon.net>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2023-03-07 16:39 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230307152825.263841-1-thomas@monjalon.net>
2023-03-07 15:17 ` qemudev
2023-03-07 15:21 ` qemudev
2023-03-07 15:29 ` |WARNING| " checkpatch
2023-03-07 17:39 ` 0-day Robot [this message]
2023-03-08  0:15 |SUCCESS| " dpdklab
2023-03-08  0:18 dpdklab
2023-03-08  0:18 dpdklab
2023-03-08  0:19 dpdklab
2023-03-08  0:20 dpdklab
2023-03-08  0:21 dpdklab
2023-03-08  0:25 dpdklab
2023-03-08  0:25 dpdklab
2023-03-08  0:27 dpdklab
2023-03-08  0:28 dpdklab
2023-03-08  0:35 dpdklab
2023-03-08  0:35 dpdklab
2023-03-08  0:36 dpdklab
2023-03-08  0:37 dpdklab
2023-03-08  0:40 dpdklab
2023-03-08  0:41 dpdklab
2023-03-08  0:42 dpdklab
2023-03-08  0:45 dpdklab
2023-03-08  0:45 dpdklab
2023-03-08  0:48 dpdklab
2023-03-08  0:48 dpdklab
2023-03-08  0:54 dpdklab
2023-03-08  0:59 dpdklab
2023-03-08  1:01 dpdklab
2023-03-08  1:11 dpdklab
2023-03-08  1:14 dpdklab
2023-03-08  1:32 dpdklab
2023-03-08  1:44 dpdklab
2023-03-08  2:03 dpdklab
2023-03-08  2:26 dpdklab
2023-03-08  2:32 dpdklab
2023-03-08  2:38 dpdklab
2023-03-08  3:29 dpdklab
2023-03-08  3:29 dpdklab
2023-03-08  4:05 dpdklab
2023-03-08  4:23 dpdklab
2023-03-08  4:23 dpdklab
2023-03-08  4:59 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=20230307173917.732461-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).