From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140730 [PATCH v2] eventdev/crypto: restore opaque field between dequeue and enqueue
Date: Tue, 4 Jun 2024 13:24:43 -0400 [thread overview]
Message-ID: <20240604172443.2152937-1-robot@bytheb.org> (raw)
In-Reply-To: <20240604161848.1575399-1-ganapati.kundapura@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140730/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9370998679
next prev parent reply other threads:[~2024-06-04 17:24 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604161848.1575399-1-ganapati.kundapura@intel.com>
2024-06-04 15:53 ` qemudev
2024-06-04 15:57 ` qemudev
2024-06-04 16:19 ` checkpatch
2024-06-04 17:24 ` 0-day Robot [this message]
2024-06-04 22:38 ` |SUCCESS| pw140730 [PATCH] [v2] eventdev/crypto: restore opaque fiel dpdklab
2024-06-04 22:55 ` dpdklab
2024-06-04 22:55 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:22 ` dpdklab
2024-06-04 23:23 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:33 ` dpdklab
2024-06-04 23:33 ` dpdklab
2024-06-04 23:33 ` dpdklab
2024-06-04 23:33 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:38 ` dpdklab
2024-06-04 23:38 ` dpdklab
2024-06-04 23:38 ` dpdklab
2024-06-04 23:39 ` dpdklab
2024-06-04 23:39 ` dpdklab
2024-06-04 23:39 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:41 ` dpdklab
2024-06-04 23:41 ` dpdklab
2024-06-04 23:41 ` dpdklab
2024-06-04 23:42 ` dpdklab
2024-06-04 23:42 ` dpdklab
2024-06-04 23:43 ` dpdklab
2024-06-04 23:44 ` dpdklab
2024-06-04 23:46 ` dpdklab
2024-06-04 23:49 ` dpdklab
2024-06-04 23:49 ` dpdklab
2024-06-04 23:54 ` dpdklab
2024-06-04 23:56 ` dpdklab
2024-06-05 0:00 ` dpdklab
2024-06-05 0:01 ` dpdklab
2024-06-05 0:03 ` dpdklab
2024-06-05 0:04 ` dpdklab
2024-06-05 0:04 ` dpdklab
2024-06-05 0:06 ` dpdklab
2024-06-05 0:06 ` dpdklab
2024-06-05 0:08 ` dpdklab
2024-06-05 0:09 ` dpdklab
2024-06-05 0:10 ` dpdklab
2024-06-05 0:10 ` dpdklab
2024-06-05 0:16 ` dpdklab
2024-06-05 0:18 ` dpdklab
2024-06-05 0:22 ` dpdklab
2024-06-05 0:22 ` dpdklab
2024-06-05 0:23 ` |WARNING| " dpdklab
2024-06-05 0:28 ` |SUCCESS| " dpdklab
2024-06-05 0:30 ` |WARNING| " dpdklab
2024-06-05 0:31 ` dpdklab
2024-06-05 0:32 ` dpdklab
2024-06-05 0:34 ` |SUCCESS| " dpdklab
2024-06-05 0:34 ` |WARNING| " dpdklab
2024-06-05 0:35 ` dpdklab
2024-06-05 0:38 ` dpdklab
2024-06-05 0:38 ` |SUCCESS| " dpdklab
2024-06-05 0:39 ` |WARNING| " dpdklab
2024-06-05 0:43 ` dpdklab
2024-06-05 0:43 ` |SUCCESS| " dpdklab
2024-06-05 0:44 ` |WARNING| " dpdklab
2024-06-05 0:44 ` |SUCCESS| " dpdklab
2024-06-05 0:45 ` |WARNING| " dpdklab
2024-06-05 0:45 ` |SUCCESS| " dpdklab
2024-06-05 0:48 ` dpdklab
2024-06-05 0:49 ` dpdklab
2024-06-05 0:49 ` dpdklab
2024-06-05 0:49 ` dpdklab
2024-06-05 0:53 ` dpdklab
2024-06-05 0:53 ` dpdklab
2024-06-05 0:54 ` dpdklab
2024-06-05 0:58 ` dpdklab
2024-06-05 0:58 ` dpdklab
2024-06-05 1:01 ` dpdklab
2024-06-05 1:02 ` dpdklab
2024-06-05 1:05 ` dpdklab
2024-06-05 1:05 ` dpdklab
2024-06-05 1:06 ` dpdklab
2024-06-05 1:09 ` dpdklab
2024-06-05 21:16 ` 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=20240604172443.2152937-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).