From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw135901 [PATCH v4] dts: add Dockerfile
Date: Tue, 16 Jan 2024 15:03:41 -0500 [thread overview]
Message-ID: <20240116200341.1811854-1-robot@bytheb.org> (raw)
In-Reply-To: <20240116191814.31316-1-jspewock@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/135901/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7546584551
next prev parent reply other threads:[~2024-01-16 20:03 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240116191814.31316-1-jspewock@iol.unh.edu>
2024-01-16 19:19 ` |WARNING| " checkpatch
2024-01-16 20:03 ` 0-day Robot [this message]
2024-01-17 2:08 ` |SUCCESS| " qemudev
2024-01-17 2:13 ` qemudev
2024-01-18 6:51 |SUCCESS| pw135901 [PATCH] [v4] " dpdklab
2024-01-18 7:06 dpdklab
2024-01-18 7:40 dpdklab
2024-01-18 7:43 dpdklab
2024-01-18 7:45 dpdklab
2024-01-18 7:47 dpdklab
2024-01-18 7:48 dpdklab
2024-01-18 7:54 dpdklab
2024-01-18 8:05 dpdklab
2024-01-18 8:06 dpdklab
2024-01-18 8:09 dpdklab
2024-01-18 8:11 dpdklab
2024-01-18 8:13 dpdklab
2024-01-18 8:15 dpdklab
2024-01-18 8:17 dpdklab
2024-01-18 8:18 dpdklab
2024-01-18 8:18 dpdklab
2024-01-18 8:20 dpdklab
2024-01-18 8:21 dpdklab
2024-01-18 8:38 dpdklab
2024-01-18 8:46 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:52 dpdklab
2024-01-18 8:52 dpdklab
2024-01-18 9:10 dpdklab
2024-01-18 9:44 dpdklab
2024-01-18 9:49 dpdklab
2024-01-18 10:21 dpdklab
2024-01-18 10:23 dpdklab
2024-01-18 10:23 dpdklab
2024-01-18 10:27 dpdklab
2024-01-18 10:37 dpdklab
2024-01-18 10:50 dpdklab
2024-01-18 10:50 dpdklab
2024-01-18 10:55 dpdklab
2024-01-18 10:56 dpdklab
2024-01-18 10:58 dpdklab
2024-01-18 10:58 dpdklab
2024-01-18 10:59 dpdklab
2024-01-18 11:02 dpdklab
2024-01-18 11:04 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:15 dpdklab
2024-01-18 11:27 dpdklab
2024-01-18 11:36 dpdklab
2024-01-18 11:37 dpdklab
2024-01-18 11:38 dpdklab
2024-01-18 11:39 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 12:11 dpdklab
2024-01-18 13:05 dpdklab
2024-01-18 14:25 dpdklab
2024-01-18 15:08 dpdklab
2024-01-23 21:45 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=20240116200341.1811854-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).