From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141405 [PATCH v12 4/4] cryptodev: remove marker fields
Date: Wed, 19 Jun 2024 12:04:48 -0400 [thread overview]
Message-ID: <20240619160448.3012828-1-robot@bytheb.org> (raw)
In-Reply-To: <20240619150126.1037902-5-david.marchand@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141405/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9584635255
next prev parent reply other threads:[~2024-06-19 16:04 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240619150126.1037902-5-david.marchand@redhat.com>
2024-06-19 14:34 ` |SUCCESS| pw141402-141405 " qemudev
2024-06-19 14:39 ` qemudev
2024-06-19 15:03 ` |SUCCESS| pw141405 " checkpatch
2024-06-19 16:04 ` 0-day Robot [this message]
2024-06-20 1:06 ` |SUCCESS| pw141402-141405 [PATCH] [v12,4/4] cryptodev: remove marker dpdklab
2024-06-20 1:21 ` dpdklab
2024-06-20 1:23 ` dpdklab
2024-06-20 1:24 ` dpdklab
2024-06-20 1:25 ` dpdklab
2024-06-20 1:27 ` dpdklab
2024-06-20 1:30 ` dpdklab
2024-06-20 1:32 ` dpdklab
2024-06-20 1:37 ` dpdklab
2024-06-20 1:48 ` dpdklab
2024-06-20 1:50 ` dpdklab
2024-06-20 1:51 ` dpdklab
2024-06-20 1:51 ` dpdklab
2024-06-20 1:52 ` dpdklab
2024-06-20 2:24 ` dpdklab
2024-06-20 2:25 ` dpdklab
2024-06-20 2:25 ` dpdklab
2024-06-20 2:28 ` dpdklab
2024-06-20 2:29 ` dpdklab
2024-06-20 2:30 ` dpdklab
2024-06-20 2:31 ` dpdklab
2024-06-20 2:33 ` dpdklab
2024-06-20 2:33 ` dpdklab
2024-06-20 2:35 ` dpdklab
2024-06-20 2:36 ` dpdklab
2024-06-20 2:38 ` dpdklab
2024-06-20 2:38 ` dpdklab
2024-06-20 2:42 ` dpdklab
2024-06-20 2:44 ` dpdklab
2024-06-20 2:57 ` dpdklab
2024-06-20 2:58 ` dpdklab
2024-06-20 2:58 ` dpdklab
2024-06-20 2:59 ` dpdklab
2024-06-20 3:01 ` dpdklab
2024-06-20 3:01 ` dpdklab
2024-06-20 3:02 ` dpdklab
2024-06-20 3:02 ` dpdklab
2024-06-20 3:03 ` dpdklab
2024-06-20 3:03 ` dpdklab
2024-06-20 3:04 ` dpdklab
2024-06-20 3:40 ` dpdklab
2024-06-20 5:09 ` dpdklab
2024-06-20 5:18 ` dpdklab
2024-06-20 5:18 ` dpdklab
2024-06-20 5:18 ` dpdklab
2024-06-20 5:19 ` dpdklab
2024-06-20 5:38 ` dpdklab
2024-06-20 6:24 ` dpdklab
2024-06-20 6:31 ` dpdklab
2024-06-20 6:32 ` dpdklab
2024-06-20 6:34 ` dpdklab
2024-06-20 6:35 ` dpdklab
2024-06-20 6:35 ` dpdklab
2024-06-20 6:35 ` dpdklab
2024-06-20 6:36 ` dpdklab
2024-06-20 6:37 ` dpdklab
2024-06-20 6:41 ` dpdklab
2024-06-20 6:42 ` dpdklab
2024-06-20 6:43 ` dpdklab
2024-06-20 6:44 ` dpdklab
2024-06-20 6:45 ` dpdklab
2024-06-20 6:46 ` dpdklab
2024-06-20 6:47 ` dpdklab
2024-06-20 6:47 ` dpdklab
2024-06-20 6:47 ` dpdklab
2024-06-20 6:48 ` dpdklab
2024-06-20 6:49 ` dpdklab
2024-06-20 6:49 ` dpdklab
2024-06-20 6:50 ` dpdklab
2024-06-20 6:51 ` dpdklab
2024-06-20 6:51 ` dpdklab
2024-06-20 6:52 ` dpdklab
2024-06-20 6:53 ` dpdklab
2024-06-20 6:54 ` dpdklab
2024-06-20 6:55 ` dpdklab
2024-06-20 6:57 ` dpdklab
2024-06-20 6:58 ` dpdklab
2024-06-20 6:58 ` dpdklab
2024-06-20 7:01 ` dpdklab
2024-06-20 7:05 ` dpdklab
2024-06-20 7:05 ` dpdklab
2024-06-20 7:06 ` dpdklab
2024-06-20 7:10 ` dpdklab
2024-06-20 7:10 ` dpdklab
2024-06-20 7:12 ` dpdklab
2024-06-20 7:16 ` dpdklab
2024-06-20 7:19 ` dpdklab
2024-06-20 7:20 ` dpdklab
2024-06-20 7:32 ` dpdklab
2024-06-20 7:35 ` dpdklab
2024-06-20 7:47 ` dpdklab
2024-06-20 7:49 ` dpdklab
2024-06-20 7:54 ` dpdklab
2024-06-20 8:00 ` dpdklab
2024-06-20 8:03 ` dpdklab
2024-06-20 8:11 ` dpdklab
2024-06-20 8:15 ` dpdklab
2024-06-20 8:27 ` dpdklab
2024-06-20 8:28 ` dpdklab
2024-06-20 8:32 ` dpdklab
2024-06-20 8:33 ` dpdklab
2024-06-20 8:45 ` dpdklab
2024-06-20 8:49 ` dpdklab
2024-06-20 9:03 ` dpdklab
2024-06-20 9:05 ` dpdklab
2024-06-20 9:09 ` dpdklab
2024-06-20 9:11 ` dpdklab
2024-06-20 9:12 ` dpdklab
2024-06-20 9:13 ` dpdklab
2024-06-20 9:30 ` dpdklab
2024-06-20 9:38 ` dpdklab
2024-06-20 9:49 ` dpdklab
2024-06-20 13:01 ` dpdklab
2024-06-20 14:18 ` dpdklab
2024-06-21 22:34 ` 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=20240619160448.3012828-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).