From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw142936 [v2 7/7] crypto/dpaa2_sec: rework debug code
Date: Tue, 6 Aug 2024 09:03:09 -0400 [thread overview]
Message-ID: <20240806130309.1982451-1-robot@bytheb.org> (raw)
In-Reply-To: <20240806102732.3225536-8-g.singh@nxp.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/142936/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10265053509
next prev parent reply other threads:[~2024-08-06 13:03 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240806102732.3225536-8-g.singh@nxp.com>
2024-08-06 10:01 ` |SUCCESS| pw142930-142936 " qemudev
2024-08-06 10:06 ` qemudev
2024-08-06 10:29 ` |SUCCESS| pw142936 " checkpatch
2024-08-06 13:03 ` 0-day Robot [this message]
2024-08-06 14:06 ` |SUCCESS| pw142930-142936 [PATCH] [v2,7/7] crypto/dpaa2_sec: rework dpdklab
2024-08-06 14:25 ` |PENDING| " dpdklab
2024-08-06 14:25 ` dpdklab
2024-08-06 14:33 ` dpdklab
2024-08-06 14:33 ` |SUCCESS| " dpdklab
2024-08-06 14:38 ` |PENDING| " dpdklab
2024-08-06 14:38 ` dpdklab
2024-08-06 14:46 ` |SUCCESS| " dpdklab
2024-08-06 14:46 ` |PENDING| " dpdklab
2024-08-06 14:51 ` |SUCCESS| " dpdklab
2024-08-06 14:56 ` dpdklab
2024-08-06 14:59 ` |PENDING| " dpdklab
2024-08-06 15:01 ` dpdklab
2024-08-06 15:03 ` dpdklab
2024-08-06 15:04 ` dpdklab
2024-08-06 15:05 ` dpdklab
2024-08-06 15:05 ` dpdklab
2024-08-06 15:06 ` |SUCCESS| " dpdklab
2024-08-06 15:07 ` dpdklab
2024-08-06 15:07 ` |PENDING| " dpdklab
2024-08-06 15:08 ` dpdklab
2024-08-06 15:08 ` |SUCCESS| " dpdklab
2024-08-06 15:11 ` dpdklab
2024-08-06 15:11 ` |PENDING| " dpdklab
2024-08-06 15:12 ` dpdklab
2024-08-06 15:13 ` dpdklab
2024-08-06 15:15 ` |SUCCESS| " dpdklab
2024-08-06 15:16 ` |PENDING| " dpdklab
2024-08-06 15:18 ` dpdklab
2024-08-06 15:19 ` dpdklab
2024-08-06 15:19 ` dpdklab
2024-08-06 15:19 ` dpdklab
2024-08-06 15:19 ` dpdklab
2024-08-06 15:20 ` dpdklab
2024-08-06 15:20 ` dpdklab
2024-08-06 15:20 ` dpdklab
2024-08-06 15:21 ` dpdklab
2024-08-06 15:21 ` dpdklab
2024-08-06 15:22 ` dpdklab
2024-08-06 15:23 ` dpdklab
2024-08-06 15:30 ` dpdklab
2024-08-06 15:30 ` dpdklab
2024-08-06 15:31 ` dpdklab
2024-08-06 15:31 ` dpdklab
2024-08-06 15:33 ` dpdklab
2024-08-06 15:33 ` dpdklab
2024-08-06 15:34 ` dpdklab
2024-08-06 15:35 ` dpdklab
2024-08-06 15:35 ` dpdklab
2024-08-06 15:35 ` dpdklab
2024-08-06 15:35 ` dpdklab
2024-08-06 15:36 ` dpdklab
2024-08-06 15:36 ` dpdklab
2024-08-06 15:36 ` dpdklab
2024-08-06 15:37 ` dpdklab
2024-08-06 15:41 ` dpdklab
2024-08-06 15:41 ` dpdklab
2024-08-06 15:42 ` dpdklab
2024-08-06 15:42 ` dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:43 ` dpdklab
2024-08-06 15:44 ` dpdklab
2024-08-06 15:45 ` dpdklab
2024-08-06 15:46 ` dpdklab
2024-08-06 15:46 ` dpdklab
2024-08-06 15:47 ` dpdklab
2024-08-06 15:48 ` dpdklab
2024-08-06 15:49 ` dpdklab
2024-08-06 15:52 ` |SUCCESS| " dpdklab
2024-08-06 15:52 ` dpdklab
2024-08-06 15:54 ` |PENDING| " dpdklab
2024-08-06 15:55 ` dpdklab
2024-08-06 15:57 ` dpdklab
2024-08-06 15:58 ` dpdklab
2024-08-06 15:59 ` dpdklab
2024-08-06 16:02 ` |SUCCESS| " dpdklab
2024-08-06 16:03 ` dpdklab
2024-08-06 16:03 ` |PENDING| " dpdklab
2024-08-06 16:04 ` dpdklab
2024-08-06 16:04 ` |SUCCESS| " dpdklab
2024-08-06 16:04 ` dpdklab
2024-08-06 16:05 ` |PENDING| " dpdklab
2024-08-06 16:06 ` dpdklab
2024-08-06 16:08 ` dpdklab
2024-08-06 16:10 ` |SUCCESS| " dpdklab
2024-08-06 16:10 ` dpdklab
2024-08-06 16:19 ` |PENDING| " dpdklab
2024-08-06 16:19 ` dpdklab
2024-08-06 16:32 ` dpdklab
2024-08-06 16:44 ` |SUCCESS| " dpdklab
2024-08-06 20:37 ` |PENDING| " dpdklab
2024-08-06 20:40 ` |SUCCESS| " dpdklab
2024-08-07 0:51 ` dpdklab
2024-08-07 4:53 ` dpdklab
2024-08-07 5:07 ` dpdklab
2024-08-07 5: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=20240806130309.1982451-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).