From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw137674 [PATCH] crypto/mlx5: add max segment assert
Date: Fri, 1 Mar 2024 08:44:13 -0500 [thread overview]
Message-ID: <20240301134413.951862-1-robot@bytheb.org> (raw)
In-Reply-To: <20240301124246.1216467-1-suanmingm@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/137674/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8111829099
next prev parent reply other threads:[~2024-03-01 13:44 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301124246.1216467-1-suanmingm@nvidia.com>
2024-03-01 12:44 ` checkpatch
2024-03-01 13:44 ` 0-day Robot [this message]
2024-03-01 15:41 ` dpdklab
2024-03-01 15:47 ` |FAILURE| " dpdklab
2024-03-01 16:07 ` |SUCCESS| " dpdklab
2024-03-01 16:12 ` |FAILURE| " dpdklab
2024-03-01 16:45 ` |SUCCESS| " dpdklab
2024-03-01 16:51 ` dpdklab
2024-03-01 16:51 ` dpdklab
2024-03-01 16:54 ` dpdklab
2024-03-01 16:55 ` dpdklab
2024-03-01 16:55 ` |FAILURE| " dpdklab
2024-03-01 17:07 ` |SUCCESS| " dpdklab
2024-03-01 17:10 ` dpdklab
2024-03-01 17:11 ` dpdklab
2024-03-01 17:12 ` dpdklab
2024-03-01 17:13 ` dpdklab
2024-03-01 17:13 ` dpdklab
2024-03-01 17:13 ` dpdklab
2024-03-01 17:15 ` dpdklab
2024-03-01 17:57 ` |FAILURE| " dpdklab
2024-03-01 18:04 ` |SUCCESS| " dpdklab
2024-03-01 18:45 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:47 ` dpdklab
2024-03-01 18:50 ` dpdklab
2024-03-01 18:54 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:56 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 18:58 ` dpdklab
2024-03-01 18:58 ` dpdklab
2024-03-01 19:09 ` dpdklab
2024-03-01 19:10 ` dpdklab
2024-03-01 19:11 ` dpdklab
2024-03-01 19:11 ` dpdklab
2024-03-01 19:12 ` dpdklab
2024-03-01 19:13 ` dpdklab
2024-03-01 19:13 ` dpdklab
2024-03-01 19:14 ` dpdklab
2024-03-01 19:14 ` dpdklab
2024-03-01 19:14 ` dpdklab
2024-03-01 19:15 ` dpdklab
2024-03-01 19:15 ` dpdklab
2024-03-01 19:17 ` dpdklab
2024-03-01 19:18 ` dpdklab
2024-03-01 19:20 ` dpdklab
2024-03-01 19:21 ` dpdklab
2024-03-01 19:22 ` dpdklab
2024-03-01 19:22 ` dpdklab
2024-03-01 19:29 ` dpdklab
2024-03-01 19:30 ` dpdklab
2024-03-01 19:31 ` dpdklab
2024-03-01 19:32 ` dpdklab
2024-03-01 19:33 ` dpdklab
2024-03-01 19:50 ` dpdklab
2024-03-01 19:59 ` dpdklab
2024-03-01 20:03 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:35 ` |FAILURE| " dpdklab
2024-03-01 20:48 ` |SUCCESS| " dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-02 0:04 ` dpdklab
2024-03-02 1:45 ` dpdklab
2024-03-02 1:53 ` dpdklab
2024-03-02 6:04 ` qemudev
2024-03-02 6:09 ` qemudev
2024-03-02 20:44 ` dpdklab
2024-03-05 11:07 ` dpdklab
2024-03-05 11:30 ` dpdklab
2024-03-05 12:14 ` 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=20240301134413.951862-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).