From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143898 [PATCH v5 8/8] zsda: add zsda crypto-session and compile file
Date: Tue, 10 Sep 2024 06:26:03 -0400 [thread overview]
Message-ID: <20240910102603.566448-1-robot@bytheb.org> (raw)
In-Reply-To: <20240910091849.3854552-7-li.hanxiao@zte.com.cn>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143898/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10790001805
next prev parent reply other threads:[~2024-09-10 10:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240910091849.3854552-7-li.hanxiao@zte.com.cn>
2024-09-10 9:23 ` checkpatch
2024-09-10 9:28 ` |SUCCESS| pw143891-143898 " qemudev
2024-09-10 9:33 ` qemudev
2024-09-10 10:26 ` 0-day Robot [this message]
2024-09-10 22:15 ` |SUCCESS| pw143891-143898 [PATCH] [v5,8/8] zsda: add zsda crypto-ses dpdklab
2024-09-10 22:31 ` dpdklab
2024-09-10 23:21 ` dpdklab
2024-09-11 1:09 ` dpdklab
2024-09-11 1:10 ` |PENDING| " dpdklab
2024-09-11 1:21 ` |FAILURE| " dpdklab
2024-09-11 1:25 ` dpdklab
2024-09-11 1:28 ` dpdklab
2024-09-11 1:32 ` dpdklab
2024-09-11 1:43 ` dpdklab
2024-09-11 1:51 ` |SUCCESS| " dpdklab
2024-09-11 1:59 ` |FAILURE| " dpdklab
2024-09-11 2:04 ` |SUCCESS| " dpdklab
2024-09-11 2:07 ` dpdklab
2024-09-11 2:20 ` dpdklab
2024-09-11 2:29 ` |FAILURE| " dpdklab
2024-09-11 2:33 ` dpdklab
2024-09-11 2:33 ` dpdklab
2024-09-11 2:38 ` dpdklab
2024-09-11 2:43 ` dpdklab
2024-09-11 2:45 ` dpdklab
2024-09-11 2:50 ` |SUCCESS| " dpdklab
2024-09-11 2:55 ` |FAILURE| " dpdklab
2024-09-11 3:02 ` dpdklab
2024-09-11 3:13 ` dpdklab
2024-09-11 3:17 ` dpdklab
2024-09-11 3:30 ` dpdklab
2024-09-11 3:55 ` |SUCCESS| " dpdklab
2024-09-11 3:57 ` |FAILURE| " dpdklab
2024-09-11 4:16 ` dpdklab
2024-09-11 4:46 ` dpdklab
2024-09-11 5:05 ` |SUCCESS| " dpdklab
2024-09-11 5:34 ` dpdklab
2024-09-15 23:24 ` dpdklab
2024-09-16 5:23 ` 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=20240910102603.566448-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).