From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138420 [PATCH v3 8/8] crypto/cnxk: update the context structure of tls
Date: Fri, 15 Mar 2024 02:43:24 -0400 [thread overview]
Message-ID: <20240315064324.2855878-1-robot@bytheb.org> (raw)
In-Reply-To: <20240315054213.540-9-vvelumuri@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138420/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8292014988
next prev parent reply other threads:[~2024-03-15 6:43 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315054213.540-9-vvelumuri@marvell.com>
2024-03-15 5:21 ` |SUCCESS| pw138413-138420 " qemudev
2024-03-15 5:26 ` qemudev
2024-03-15 5:46 ` |SUCCESS| pw138420 " checkpatch
2024-03-15 6:43 ` |SUCCESS| pw138413-138420 [PATCH] [v3,8/8] crypto/cnxk: update the c dpdklab
2024-03-15 6:43 ` 0-day Robot [this message]
2024-03-15 6:54 ` dpdklab
2024-03-15 7:00 ` dpdklab
2024-03-15 7:01 ` dpdklab
2024-03-15 7:01 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:04 ` dpdklab
2024-03-15 7:04 ` dpdklab
2024-03-15 7:06 ` dpdklab
2024-03-15 7:06 ` dpdklab
2024-03-15 7:07 ` dpdklab
2024-03-15 7:07 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:10 ` dpdklab
2024-03-15 7:10 ` dpdklab
2024-03-15 7:11 ` dpdklab
2024-03-15 7:12 ` dpdklab
2024-03-15 7:12 ` dpdklab
2024-03-15 7:14 ` dpdklab
2024-03-15 7:14 ` dpdklab
2024-03-15 7:15 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:21 ` dpdklab
2024-03-15 7:22 ` dpdklab
2024-03-15 7:23 ` dpdklab
2024-03-15 7:44 ` dpdklab
2024-03-15 7:46 ` dpdklab
2024-03-15 7:47 ` dpdklab
2024-03-15 7:47 ` dpdklab
2024-03-15 7:49 ` dpdklab
2024-03-15 7:51 ` dpdklab
2024-03-15 7:52 ` dpdklab
2024-03-15 7:53 ` dpdklab
2024-03-15 7:53 ` dpdklab
2024-03-15 7:54 ` dpdklab
2024-03-15 7:54 ` dpdklab
2024-03-15 7:55 ` dpdklab
2024-03-15 7:58 ` dpdklab
2024-03-15 7:58 ` dpdklab
2024-03-15 7:59 ` dpdklab
2024-03-15 8:00 ` dpdklab
2024-03-15 8:00 ` dpdklab
2024-03-15 8:01 ` dpdklab
2024-03-15 8:02 ` dpdklab
2024-03-15 8:04 ` dpdklab
2024-03-15 8:05 ` dpdklab
2024-03-15 8:41 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-19 0:31 ` dpdklab
2024-03-19 1:08 ` 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=20240315064324.2855878-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).