automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141139 [PATCH v2 2/2] crypto/mlx5: add out of place mode for IPsec operation
Date: Thu, 13 Jun 2024 21:24:40 -0400	[thread overview]
Message-ID: <20240614012440.4025141-1-robot@bytheb.org> (raw)
In-Reply-To: <20240614003031.2006131-3-suanmingm@nvidia.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141139/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9508806102

  parent reply	other threads:[~2024-06-14  1:24 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240614003031.2006131-3-suanmingm@nvidia.com>
2024-06-14  0:03 ` |SUCCESS| pw141138-141139 " qemudev
2024-06-14  0:08 ` qemudev
2024-06-14  0:31 ` |SUCCESS| pw141139 " checkpatch
2024-06-14  1:24 ` 0-day Robot [this message]
2024-06-14  8:26 ` |SUCCESS| pw141138-141139 [PATCH] [v2,2/2] crypto/mlx5: add out of p dpdklab
2024-06-14  8:38 ` dpdklab
2024-06-14  8:40 ` dpdklab
2024-06-14  8:41 ` dpdklab
2024-06-14  8:41 ` dpdklab
2024-06-14  8:43 ` dpdklab
2024-06-14  8:45 ` dpdklab
2024-06-14  8:46 ` dpdklab
2024-06-14  8:48 ` dpdklab
2024-06-14  8:48 ` dpdklab
2024-06-14  8:53 ` dpdklab
2024-06-14  8:57 ` dpdklab
2024-06-14  9:18 ` dpdklab
2024-06-14  9:43 ` dpdklab
2024-06-14  9:46 ` dpdklab
2024-06-14  9:48 ` dpdklab
2024-06-14  9:51 ` dpdklab
2024-06-14 10:04 ` dpdklab
2024-06-14 10:06 ` dpdklab
2024-06-14 10:07 ` dpdklab
2024-06-14 10:12 ` dpdklab
2024-06-14 10:13 ` dpdklab
2024-06-14 10:15 ` dpdklab
2024-06-14 10:16 ` dpdklab
2024-06-14 10:17 ` dpdklab
2024-06-14 10:18 ` dpdklab
2024-06-14 10:19 ` dpdklab
2024-06-14 10:19 ` dpdklab
2024-06-14 10:22 ` dpdklab
2024-06-14 10:23 ` dpdklab
2024-06-14 10:24 ` dpdklab
2024-06-14 10:25 ` dpdklab
2024-06-14 10:26 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:29 ` dpdklab
2024-06-14 10:37 ` dpdklab
2024-06-14 10:38 ` dpdklab
2024-06-14 10:38 ` dpdklab
2024-06-14 10:39 ` dpdklab
2024-06-14 10:39 ` dpdklab
2024-06-14 10:39 ` dpdklab
2024-06-14 10:40 ` dpdklab
2024-06-14 10:40 ` dpdklab
2024-06-14 10:41 ` dpdklab
2024-06-14 10:41 ` dpdklab
2024-06-14 10:41 ` dpdklab
2024-06-14 10:50 ` dpdklab
2024-06-14 10:52 ` dpdklab
2024-06-14 10:53 ` dpdklab
2024-06-14 10:54 ` dpdklab
2024-06-14 10:55 ` dpdklab
2024-06-14 10:55 ` dpdklab
2024-06-14 10:55 ` dpdklab
2024-06-14 10:57 ` dpdklab
2024-06-14 10:58 ` dpdklab
2024-06-14 10:58 ` dpdklab
2024-06-14 10:59 ` dpdklab
2024-06-14 10:59 ` dpdklab
2024-06-14 11:00 ` dpdklab
2024-06-14 11:00 ` dpdklab
2024-06-14 11:00 ` dpdklab
2024-06-14 11:01 ` dpdklab
2024-06-14 11:01 ` dpdklab
2024-06-14 11:02 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:05 ` dpdklab
2024-06-14 11:08 ` dpdklab
2024-06-14 11:09 ` dpdklab
2024-06-14 11:17 ` dpdklab
2024-06-14 11:17 ` dpdklab
2024-06-14 11:19 ` dpdklab
2024-06-14 11:19 ` dpdklab
2024-06-14 11:20 ` dpdklab
2024-06-14 11:20 ` dpdklab
2024-06-14 11:20 ` dpdklab
2024-06-14 11:21 ` dpdklab
2024-06-14 11:21 ` dpdklab
2024-06-14 11:22 ` dpdklab
2024-06-14 11:22 ` dpdklab
2024-06-14 11:22 ` dpdklab
2024-06-14 11:23 ` dpdklab
2024-06-14 11:29 ` dpdklab
2024-06-14 11:35 ` dpdklab
2024-06-14 11:35 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:37 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:49 ` dpdklab
2024-06-14 11:49 ` dpdklab
2024-06-14 11:56 ` dpdklab
2024-06-14 11:58 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 12:07 ` dpdklab
2024-06-14 12:56 ` 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=20240614012440.4025141-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).