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| pw141134 [PATCH 4/4] dts: Rework DPDK Attributes In SUT Node Config
Date: Thu, 13 Jun 2024 17:24:49 -0400	[thread overview]
Message-ID: <20240613212449.3600470-1-robot@bytheb.org> (raw)
In-Reply-To: <20240613201831.9748-11-npratte@iol.unh.edu>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-06-13 21:24 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240613201831.9748-11-npratte@iol.unh.edu>
2024-06-13 20:00 ` |SUCCESS| pw141131-141134 " qemudev
2024-06-13 20:05 ` qemudev
2024-06-13 20:23 ` |SUCCESS| pw141134 " checkpatch
2024-06-13 21:24 ` 0-day Robot [this message]
2024-06-14  0:29 ` |SUCCESS| pw141131-141134 [PATCH] [4/4] dts: Rework DPDK Attributes dpdklab
2024-06-14  0:30 ` dpdklab
2024-06-14  0:32 ` dpdklab
2024-06-14  0:35 ` dpdklab
2024-06-14  0:36 ` dpdklab
2024-06-14  0:43 ` dpdklab
2024-06-14  0:44 ` dpdklab
2024-06-14  0:46 ` dpdklab
2024-06-14  0:46 ` dpdklab
2024-06-14  0:46 ` dpdklab
2024-06-14  0:54 ` dpdklab
2024-06-14  1:07 ` dpdklab
2024-06-14  1:09 ` dpdklab
2024-06-14  1:12 ` dpdklab
2024-06-14  1:27 ` dpdklab
2024-06-14  1:28 ` dpdklab
2024-06-14  1:31 ` dpdklab
2024-06-14  1:33 ` dpdklab
2024-06-14  1:33 ` dpdklab
2024-06-14  1:34 ` dpdklab
2024-06-14  1:34 ` dpdklab
2024-06-14  1:35 ` dpdklab
2024-06-14  1:35 ` dpdklab
2024-06-14  1:39 ` dpdklab
2024-06-14  1:40 ` dpdklab
2024-06-14  1:42 ` dpdklab
2024-06-14  1:43 ` dpdklab
2024-06-14  1:44 ` dpdklab
2024-06-14  1:46 ` dpdklab
2024-06-14  1:47 ` dpdklab
2024-06-14  1:48 ` dpdklab
2024-06-14  1:49 ` dpdklab
2024-06-14  1:51 ` dpdklab
2024-06-14  1:51 ` dpdklab
2024-06-14  1:51 ` dpdklab
2024-06-14  1:52 ` dpdklab
2024-06-14  1:52 ` dpdklab
2024-06-14  1:52 ` dpdklab
2024-06-14  1:54 ` dpdklab
2024-06-14  2:10 ` dpdklab
2024-06-14  2:10 ` dpdklab
2024-06-14  2:11 ` dpdklab
2024-06-14  2:13 ` dpdklab
2024-06-14  2:14 ` dpdklab
2024-06-14  2:15 ` dpdklab
2024-06-14  2:15 ` dpdklab
2024-06-14  2:17 ` dpdklab
2024-06-14  2:18 ` dpdklab
2024-06-14  2:18 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:19 ` dpdklab
2024-06-14  2:20 ` dpdklab
2024-06-14  2:20 ` dpdklab
2024-06-14  2:20 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:21 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:22 ` dpdklab
2024-06-14  2:23 ` dpdklab
2024-06-14  2:23 ` dpdklab
2024-06-14  2:23 ` dpdklab
2024-06-14  2:24 ` dpdklab
2024-06-14  2:24 ` dpdklab
2024-06-14  2:24 ` dpdklab
2024-06-14  2:24 ` dpdklab
2024-06-14  2:24 ` dpdklab
2024-06-14  2:25 ` dpdklab
2024-06-14  2:25 ` dpdklab
2024-06-14  2:33 ` dpdklab
2024-06-14  2:35 ` dpdklab
2024-06-14  2:35 ` dpdklab
2024-06-14  2:37 ` dpdklab
2024-06-14  2:37 ` dpdklab
2024-06-14  2:38 ` dpdklab
2024-06-14  2:40 ` dpdklab
2024-06-14  2:46 ` dpdklab
2024-06-14  2:47 ` dpdklab
2024-06-14  2:48 ` dpdklab
2024-06-14  2:49 ` dpdklab
2024-06-14  2:51 ` dpdklab
2024-06-14  2:58 ` dpdklab
2024-06-14  2:58 ` dpdklab
2024-06-14  2:59 ` dpdklab
2024-06-14  3:00 ` dpdklab
2024-06-14  3:03 ` dpdklab
2024-06-14  3:05 ` dpdklab
2024-06-14  3:05 ` dpdklab
2024-06-14  3:10 ` dpdklab
2024-06-14  4:37 ` dpdklab
2024-06-14  4:52 ` dpdklab
2024-06-14  5:33 ` 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=20240613212449.3600470-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).