From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw139557 [PATCH 6/6] crypto/ionic: add documentation and connect to build
Date: Fri, 19 Apr 2024 16:44:15 -0400 [thread overview]
Message-ID: <20240419204415.1672786-1-robot@bytheb.org> (raw)
In-Reply-To: <20240419195310.21432-7-andrew.boyer@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/139557/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8759005577
next prev parent reply other threads:[~2024-04-19 20:44 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419195310.21432-7-andrew.boyer@amd.com>
2024-04-19 19:55 ` checkpatch
2024-04-19 20:44 ` 0-day Robot [this message]
2024-04-19 21:03 ` |SUCCESS| pw139553-139557 [PATCH] [6/6] crypto/ionic: add documentat dpdklab
2024-04-19 21:03 ` dpdklab
2024-04-19 21:04 ` dpdklab
2024-04-19 21:05 ` dpdklab
2024-04-19 21:05 ` dpdklab
2024-04-19 21:05 ` dpdklab
2024-04-19 21:06 ` dpdklab
2024-04-19 21:06 ` dpdklab
2024-04-19 21:07 ` dpdklab
2024-04-19 21:08 ` dpdklab
2024-04-19 21:09 ` dpdklab
2024-04-19 21:10 ` dpdklab
2024-04-19 21:10 ` dpdklab
2024-04-19 21:11 ` dpdklab
2024-04-19 21:11 ` dpdklab
2024-04-19 21:12 ` dpdklab
2024-04-19 21:13 ` dpdklab
2024-04-19 21:13 ` dpdklab
2024-04-19 21:14 ` dpdklab
2024-04-19 21:15 ` dpdklab
2024-04-19 21:16 ` dpdklab
2024-04-19 21:16 ` dpdklab
2024-04-19 21:16 ` dpdklab
2024-04-19 21:17 ` dpdklab
2024-04-19 21:17 ` dpdklab
2024-04-19 21:17 ` dpdklab
2024-04-19 21:17 ` dpdklab
2024-04-19 21:18 ` dpdklab
2024-04-19 21:18 ` dpdklab
2024-04-19 21:19 ` dpdklab
2024-04-19 21:19 ` dpdklab
2024-04-19 21:19 ` dpdklab
2024-04-19 21:19 ` dpdklab
2024-04-19 21:19 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:20 ` dpdklab
2024-04-19 21:21 ` dpdklab
2024-04-19 21:21 ` dpdklab
2024-04-19 21:21 ` dpdklab
2024-04-19 21:21 ` dpdklab
2024-04-19 21:21 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:22 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:23 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:24 ` dpdklab
2024-04-19 21:25 ` dpdklab
2024-04-19 21:27 ` dpdklab
2024-04-19 21:27 ` dpdklab
2024-04-19 21:27 ` dpdklab
2024-04-19 21:28 ` dpdklab
2024-04-19 21:30 ` dpdklab
2024-04-19 21:31 ` dpdklab
2024-04-19 21:31 ` dpdklab
2024-04-19 21:33 ` dpdklab
2024-04-19 21:33 ` dpdklab
2024-04-19 21:34 ` dpdklab
2024-04-19 21:35 ` dpdklab
2024-04-19 21:36 ` dpdklab
2024-04-19 21:38 ` dpdklab
2024-04-19 21:39 ` dpdklab
2024-04-19 21:41 ` dpdklab
2024-04-19 21:46 ` dpdklab
2024-04-19 21:53 ` dpdklab
2024-04-19 21:58 ` dpdklab
2024-04-19 22:05 ` dpdklab
2024-04-19 22:10 ` dpdklab
2024-04-19 22:30 ` dpdklab
2024-04-19 23:26 ` dpdklab
2024-04-20 0:03 ` dpdklab
2024-04-20 0:07 ` dpdklab
2024-04-22 2:07 ` |SUCCESS| pw139553-139557 [PATCH 6/6] crypto/ionic: add documentation and connect to build qemudev
2024-04-22 2:11 ` qemudev
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=20240419204415.1672786-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).