From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw123589 [PATCH v3] test: add cryptodev crosscheck suite
Date: Thu, 9 Feb 2023 10:39:23 -0500 [thread overview]
Message-ID: <20230209153923.3390766-1-robot@bytheb.org> (raw)
In-Reply-To: <20230209143419.2181384-1-vfialko@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/123589/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4135374664
next prev parent reply other threads:[~2023-02-09 15:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209143419.2181384-1-vfialko@marvell.com>
2023-02-09 14:23 ` qemudev
2023-02-09 14:27 ` qemudev
2023-02-09 14:36 ` checkpatch
2023-02-09 15:39 ` 0-day Robot [this message]
2023-02-09 15:01 |SUCCESS| pw123589 [PATCH] [v3] " dpdklab
2023-02-09 15:01 dpdklab
2023-02-09 15:05 dpdklab
2023-02-09 15:06 dpdklab
2023-02-09 15:07 dpdklab
2023-02-09 15:13 dpdklab
2023-02-09 15:13 dpdklab
2023-02-09 15:13 dpdklab
2023-02-09 15:16 dpdklab
2023-02-09 15:18 dpdklab
2023-02-09 15:20 dpdklab
2023-02-09 15:22 dpdklab
2023-02-09 15:42 dpdklab
2023-02-09 16:42 dpdklab
2023-02-11 3:57 dpdklab
2023-02-11 4:00 dpdklab
2023-02-11 4:10 dpdklab
2023-02-11 4:23 dpdklab
2023-02-11 4:24 dpdklab
2023-02-11 4:26 dpdklab
2023-02-11 4:31 dpdklab
2023-02-11 4:43 dpdklab
2023-02-11 4:48 dpdklab
2023-02-11 4:50 dpdklab
2023-02-11 4:51 dpdklab
2023-02-11 4:53 dpdklab
2023-02-11 4:55 dpdklab
2023-02-11 4:55 dpdklab
2023-02-12 20:44 dpdklab
2023-02-12 21:07 dpdklab
2023-02-17 3:40 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=20230209153923.3390766-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).