From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141917 [PATCH] app/eventdev: increase default queue depth for cryptodev
Date: Thu, 27 Jun 2024 02:05:54 -0400 [thread overview]
Message-ID: <20240627060554.159884-1-robot@bytheb.org> (raw)
In-Reply-To: <20240627051524.1682347-1-asasidharan@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141917/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9691182589
next prev parent reply other threads:[~2024-06-27 6:07 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240627051524.1682347-1-asasidharan@marvell.com>
2024-06-27 4:55 ` qemudev
2024-06-27 5:00 ` qemudev
2024-06-27 5:16 ` checkpatch
2024-06-27 6:05 ` 0-day Robot [this message]
2024-06-27 15:47 ` |SUCCESS| pw141917 [PATCH] app/eventdev: increase default queue dept dpdklab
2024-06-27 17:03 ` dpdklab
2024-06-27 17:17 ` dpdklab
2024-06-27 17:50 ` dpdklab
2024-06-27 18:03 ` dpdklab
2024-06-27 18:47 ` |PENDING| " dpdklab
2024-06-27 18:53 ` dpdklab
2024-06-27 19:10 ` dpdklab
2024-06-27 19:11 ` dpdklab
2024-06-27 19:18 ` dpdklab
2024-06-27 19:19 ` dpdklab
2024-06-27 19:19 ` dpdklab
2024-06-27 19:21 ` dpdklab
2024-06-27 19:22 ` dpdklab
2024-06-27 19:24 ` dpdklab
2024-06-27 19:33 ` dpdklab
2024-06-27 19:35 ` dpdklab
2024-06-27 19:40 ` dpdklab
2024-06-27 19:45 ` dpdklab
2024-06-27 19:47 ` dpdklab
2024-06-27 19:58 ` |SUCCESS| " dpdklab
2024-06-27 20:00 ` dpdklab
2024-06-27 20:16 ` dpdklab
2024-06-27 20:23 ` dpdklab
2024-06-27 20:37 ` dpdklab
2024-06-27 21:37 ` dpdklab
2024-06-27 21:39 ` dpdklab
2024-06-27 21:42 ` dpdklab
2024-06-27 21:44 ` dpdklab
2024-06-27 22:21 ` dpdklab
2024-06-27 22:22 ` dpdklab
2024-06-27 23:06 ` dpdklab
2024-06-27 23:15 ` dpdklab
2024-06-27 23:49 ` dpdklab
2024-06-28 1:07 ` dpdklab
2024-06-28 1:12 ` dpdklab
2024-06-28 1:17 ` dpdklab
2024-06-28 1:47 ` dpdklab
2024-06-28 2:23 ` dpdklab
2024-06-28 2:28 ` dpdklab
2024-06-28 2:30 ` dpdklab
2024-06-28 2:31 ` dpdklab
2024-06-28 2:33 ` dpdklab
2024-06-28 2:38 ` dpdklab
2024-06-28 2:39 ` dpdklab
2024-06-28 2:41 ` dpdklab
2024-06-28 2:41 ` dpdklab
2024-06-28 2:43 ` dpdklab
2024-06-28 2:43 ` dpdklab
2024-06-28 2:44 ` dpdklab
2024-06-28 2:44 ` dpdklab
2024-06-28 2:44 ` dpdklab
2024-06-28 2:44 ` dpdklab
2024-06-28 2:45 ` dpdklab
2024-06-28 2:46 ` dpdklab
2024-06-28 2:46 ` dpdklab
2024-06-28 2:48 ` dpdklab
2024-06-28 2:49 ` dpdklab
2024-06-28 2:51 ` dpdklab
2024-06-28 2:52 ` dpdklab
2024-06-28 2:52 ` dpdklab
2024-06-28 2:53 ` dpdklab
2024-06-28 2:53 ` dpdklab
2024-06-28 2:55 ` dpdklab
2024-06-28 2:57 ` dpdklab
2024-06-28 2:57 ` dpdklab
2024-06-28 2:58 ` dpdklab
2024-06-28 3:00 ` dpdklab
2024-06-28 3:01 ` dpdklab
2024-06-28 3:03 ` dpdklab
2024-06-28 3:05 ` dpdklab
2024-06-28 3:08 ` dpdklab
2024-06-28 3:25 ` dpdklab
2024-06-28 3:25 ` dpdklab
2024-06-28 3:26 ` dpdklab
2024-06-28 3:27 ` dpdklab
2024-06-28 3:31 ` dpdklab
2024-06-28 3:33 ` dpdklab
2024-06-28 3:34 ` dpdklab
2024-06-28 3:35 ` dpdklab
2024-06-28 3:38 ` dpdklab
2024-06-28 3:40 ` dpdklab
2024-06-28 3:41 ` dpdklab
2024-06-28 3:45 ` dpdklab
2024-06-28 3:49 ` dpdklab
2024-06-28 3:51 ` dpdklab
2024-06-28 3:53 ` dpdklab
2024-06-28 4:45 ` dpdklab
2024-06-28 4:57 ` dpdklab
2024-06-28 5:00 ` dpdklab
2024-06-28 5:02 ` dpdklab
2024-06-28 5:07 ` dpdklab
2024-06-28 5:08 ` dpdklab
2024-06-28 5:09 ` dpdklab
2024-06-28 5:15 ` dpdklab
2024-06-28 5:16 ` dpdklab
2024-06-28 5:23 ` dpdklab
2024-06-28 5:37 ` dpdklab
2024-06-28 5:43 ` dpdklab
2024-06-28 5:45 ` dpdklab
2024-06-28 5:48 ` dpdklab
2024-06-28 5:50 ` dpdklab
2024-06-28 5:52 ` dpdklab
2024-06-28 5:53 ` dpdklab
2024-06-28 5:55 ` dpdklab
2024-06-28 5:55 ` dpdklab
2024-06-28 14:46 ` dpdklab
2024-06-28 15:02 ` dpdklab
2024-06-29 3:54 ` 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=20240627060554.159884-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).