From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141531 [PATCH v3 2/2] crypto/mlx5: add out of place mode for IPsec operation
Date: Mon, 24 Jun 2024 11:18:44 +0200 (CEST) [thread overview]
Message-ID: <20240624091844.BF476128144@dpdk.org> (raw)
In-Reply-To: <20240624091651.2295533-3-suanmingm@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141531
_coding style OK_
next prev parent reply other threads:[~2024-06-24 9:18 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624091651.2295533-3-suanmingm@nvidia.com>
2024-06-24 8:51 ` |SUCCESS| pw141530-141531 " qemudev
2024-06-24 8:56 ` qemudev
2024-06-24 9:18 ` checkpatch [this message]
2024-06-24 10:04 ` |SUCCESS| pw141531 " 0-day Robot
2024-06-24 13:46 ` |SUCCESS| pw141530-141531 [PATCH] [v3,2/2] crypto/mlx5: add out of p dpdklab
2024-06-24 13:47 ` dpdklab
2024-06-24 13:48 ` dpdklab
2024-06-24 13:49 ` dpdklab
2024-06-24 13:50 ` dpdklab
2024-06-24 13:51 ` dpdklab
2024-06-24 13:52 ` dpdklab
2024-06-24 13:53 ` dpdklab
2024-06-24 14:06 ` dpdklab
2024-06-24 14:13 ` dpdklab
2024-06-24 14:14 ` dpdklab
2024-06-24 14:14 ` dpdklab
2024-06-24 14:16 ` dpdklab
2024-06-24 14:19 ` dpdklab
2024-06-24 14:24 ` dpdklab
2024-06-24 14:25 ` dpdklab
2024-06-24 14:25 ` dpdklab
2024-06-24 15:30 ` dpdklab
2024-06-24 15:30 ` dpdklab
2024-06-24 15:30 ` dpdklab
2024-06-24 15:31 ` dpdklab
2024-06-24 15:31 ` dpdklab
2024-06-24 15:31 ` dpdklab
2024-06-24 15:31 ` dpdklab
2024-06-24 15:31 ` dpdklab
2024-06-24 15:32 ` dpdklab
2024-06-24 15:32 ` dpdklab
2024-06-24 15:33 ` dpdklab
2024-06-24 15:34 ` dpdklab
2024-06-24 15:34 ` dpdklab
2024-06-24 15:34 ` dpdklab
2024-06-24 15:35 ` dpdklab
2024-06-24 15:35 ` dpdklab
2024-06-24 15:35 ` dpdklab
2024-06-24 15:36 ` dpdklab
2024-06-24 15:36 ` dpdklab
2024-06-24 15:36 ` dpdklab
2024-06-24 15:36 ` dpdklab
2024-06-24 15:42 ` dpdklab
2024-06-24 15:49 ` dpdklab
2024-06-24 15:52 ` dpdklab
2024-06-24 15:52 ` dpdklab
2024-06-24 15:52 ` dpdklab
2024-06-24 15:53 ` dpdklab
2024-06-24 15:54 ` dpdklab
2024-06-24 15:54 ` dpdklab
2024-06-24 15:54 ` dpdklab
2024-06-24 15:54 ` dpdklab
2024-06-24 15:55 ` dpdklab
2024-06-24 15:55 ` dpdklab
2024-06-24 15:56 ` dpdklab
2024-06-24 15:56 ` dpdklab
2024-06-24 15:57 ` dpdklab
2024-06-24 15:58 ` dpdklab
2024-06-24 15:59 ` dpdklab
2024-06-24 15:59 ` dpdklab
2024-06-24 16:02 ` dpdklab
2024-06-24 16:03 ` dpdklab
2024-06-24 16:03 ` dpdklab
2024-06-24 16:03 ` dpdklab
2024-06-24 16:06 ` dpdklab
2024-06-24 16:07 ` dpdklab
2024-06-24 16:08 ` dpdklab
2024-06-24 16:08 ` dpdklab
2024-06-24 16:09 ` dpdklab
2024-06-24 16:32 ` dpdklab
2024-06-24 16:33 ` dpdklab
2024-06-24 16:40 ` dpdklab
2024-06-24 16:44 ` dpdklab
2024-06-24 16:44 ` dpdklab
2024-06-24 16:48 ` dpdklab
2024-06-24 17:01 ` dpdklab
2024-06-24 17:02 ` dpdklab
2024-06-24 17:02 ` dpdklab
2024-06-24 17:05 ` dpdklab
2024-06-24 17:05 ` dpdklab
2024-06-24 17:05 ` dpdklab
2024-06-24 17:06 ` dpdklab
2024-06-24 17:07 ` dpdklab
2024-06-24 17:07 ` dpdklab
2024-06-24 17:08 ` dpdklab
2024-06-24 17:09 ` dpdklab
2024-06-24 17:10 ` dpdklab
2024-06-24 17:11 ` dpdklab
2024-06-24 17:12 ` dpdklab
2024-06-24 17:14 ` dpdklab
2024-06-24 17:15 ` dpdklab
2024-06-24 17:16 ` dpdklab
2024-06-24 17:20 ` dpdklab
2024-06-24 17:22 ` dpdklab
2024-06-24 17:22 ` dpdklab
2024-06-24 17:23 ` dpdklab
2024-06-24 17:29 ` dpdklab
2024-06-24 17:30 ` dpdklab
2024-06-24 17:32 ` dpdklab
2024-06-24 17:33 ` dpdklab
2024-06-24 17:35 ` dpdklab
2024-06-24 17:37 ` dpdklab
2024-06-24 17:40 ` dpdklab
2024-06-24 17:41 ` dpdklab
2024-06-24 17:41 ` dpdklab
2024-06-24 17:45 ` dpdklab
2024-06-24 17:45 ` dpdklab
2024-06-24 17:46 ` dpdklab
2024-06-24 17:50 ` dpdklab
2024-06-24 17:54 ` dpdklab
2024-06-24 17:56 ` dpdklab
2024-06-24 17:57 ` dpdklab
2024-06-24 18:02 ` dpdklab
2024-06-24 21:51 ` 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=20240624091844.BF476128144@dpdk.org \
--to=checkpatch@dpdk.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).