From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141284 [PATCH v2] app/test-crypto-perf: add shared session option
Date: Tue, 18 Jun 2024 12:44:34 -0400 [thread overview]
Message-ID: <20240618164434.1372013-1-robot@bytheb.org> (raw)
In-Reply-To: <20240618154829.474074-1-jack.bond-preston@foss.arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141284/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9568429176
next prev parent reply other threads:[~2024-06-18 16:44 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618154829.474074-1-jack.bond-preston@foss.arm.com>
2024-06-18 15:27 ` qemudev
2024-06-18 15:31 ` qemudev
2024-06-18 15:50 ` checkpatch
2024-06-18 16:44 ` 0-day Robot [this message]
2024-06-19 1:04 ` |SUCCESS| pw141284 [PATCH] [v2] app/test-crypto-perf: add shared ses dpdklab
2024-06-19 1:05 ` dpdklab
2024-06-19 1:05 ` dpdklab
2024-06-19 1:06 ` dpdklab
2024-06-19 1:06 ` dpdklab
2024-06-19 1:07 ` dpdklab
2024-06-19 1:08 ` dpdklab
2024-06-19 1:09 ` dpdklab
2024-06-19 1:11 ` dpdklab
2024-06-19 1:12 ` dpdklab
2024-06-19 1:13 ` dpdklab
2024-06-19 1:15 ` dpdklab
2024-06-19 1:17 ` dpdklab
2024-06-19 1:24 ` dpdklab
2024-06-19 1:50 ` dpdklab
2024-06-19 1:55 ` dpdklab
2024-06-19 2:32 ` dpdklab
2024-06-19 2:34 ` dpdklab
2024-06-19 2:34 ` dpdklab
2024-06-19 2:35 ` dpdklab
2024-06-19 2:36 ` dpdklab
2024-06-19 2:37 ` dpdklab
2024-06-19 2:37 ` dpdklab
2024-06-19 2:38 ` dpdklab
2024-06-19 2:40 ` dpdklab
2024-06-19 2:40 ` dpdklab
2024-06-19 2:41 ` dpdklab
2024-06-19 2:54 ` dpdklab
2024-06-19 2:54 ` dpdklab
2024-06-19 2:55 ` dpdklab
2024-06-19 2:56 ` dpdklab
2024-06-19 2:56 ` dpdklab
2024-06-19 2:56 ` dpdklab
2024-06-19 2:57 ` dpdklab
2024-06-19 3:03 ` dpdklab
2024-06-19 3:04 ` dpdklab
2024-06-19 3:05 ` dpdklab
2024-06-19 3:06 ` dpdklab
2024-06-19 3:11 ` dpdklab
2024-06-19 3:43 ` dpdklab
2024-06-19 6:09 ` dpdklab
2024-06-19 6:10 ` dpdklab
2024-06-19 6:10 ` dpdklab
2024-06-19 6:13 ` dpdklab
2024-06-19 6:15 ` dpdklab
2024-06-19 6:16 ` dpdklab
2024-06-19 6:16 ` dpdklab
2024-06-19 6:17 ` dpdklab
2024-06-19 6:18 ` dpdklab
2024-06-19 6:19 ` dpdklab
2024-06-19 6:19 ` dpdklab
2024-06-19 6:19 ` dpdklab
2024-06-19 6:20 ` dpdklab
2024-06-19 6:22 ` dpdklab
2024-06-19 6:23 ` dpdklab
2024-06-19 6:23 ` dpdklab
2024-06-19 6:24 ` dpdklab
2024-06-19 6:26 ` dpdklab
2024-06-19 6:27 ` dpdklab
2024-06-19 6:27 ` dpdklab
2024-06-19 7:00 ` dpdklab
2024-06-19 7:02 ` dpdklab
2024-06-19 7:03 ` dpdklab
2024-06-19 7:03 ` dpdklab
2024-06-19 7:04 ` dpdklab
2024-06-19 7:04 ` dpdklab
2024-06-19 7:05 ` dpdklab
2024-06-19 7:05 ` dpdklab
2024-06-19 7:05 ` dpdklab
2024-06-19 7:07 ` dpdklab
2024-06-19 7:08 ` dpdklab
2024-06-19 7:08 ` dpdklab
2024-06-19 7:08 ` dpdklab
2024-06-19 7:09 ` dpdklab
2024-06-19 7:11 ` dpdklab
2024-06-19 7:13 ` dpdklab
2024-06-19 7:14 ` dpdklab
2024-06-19 7:16 ` dpdklab
2024-06-19 7:16 ` dpdklab
2024-06-19 7:28 ` dpdklab
2024-06-19 7:30 ` dpdklab
2024-06-19 7:31 ` dpdklab
2024-06-19 7:35 ` dpdklab
2024-06-19 7:54 ` dpdklab
2024-06-19 8:28 ` dpdklab
2024-06-19 8:37 ` dpdklab
2024-06-19 8:40 ` dpdklab
2024-06-19 9:14 ` dpdklab
2024-06-19 9:14 ` dpdklab
2024-06-19 9:16 ` dpdklab
2024-06-19 9:16 ` dpdklab
2024-06-19 9:17 ` dpdklab
2024-06-19 10:40 ` dpdklab
2024-06-19 10:42 ` dpdklab
2024-06-19 10:44 ` dpdklab
2024-06-19 10:53 ` dpdklab
2024-06-19 10:54 ` dpdklab
2024-06-19 10:55 ` dpdklab
2024-06-19 10:56 ` dpdklab
2024-06-19 11:00 ` dpdklab
2024-06-19 11:11 ` dpdklab
2024-06-19 11:14 ` dpdklab
2024-06-19 11:15 ` dpdklab
2024-06-19 11:16 ` dpdklab
2024-06-19 11:23 ` dpdklab
2024-06-19 11:27 ` dpdklab
2024-06-19 11:35 ` dpdklab
2024-06-19 11:40 ` dpdklab
2024-06-19 11:47 ` dpdklab
2024-06-19 11:50 ` dpdklab
2024-06-19 18:17 ` dpdklab
2024-06-19 18:43 ` dpdklab
2024-06-21 1:09 ` 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=20240618164434.1372013-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).