From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw134005 [PATCH] crypto/mlx5: fix crypto dev leak
Date: Thu, 9 Nov 2023 08:34:38 +0100 (CET) [thread overview]
Message-ID: <20231109073438.D82D6120DB4@dpdk.org> (raw)
In-Reply-To: <20231109073317.1311513-1-suanmingm@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/134005
_coding style OK_
next prev parent reply other threads:[~2023-11-09 7:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231109073317.1311513-1-suanmingm@nvidia.com>
2023-11-09 7:20 ` qemudev
2023-11-09 7:24 ` qemudev
2023-11-09 7:34 ` checkpatch [this message]
2023-11-09 8:39 ` 0-day Robot
2023-11-09 9:59 dpdklab
2023-11-09 10:00 dpdklab
2023-11-09 10:02 dpdklab
2023-11-09 10:04 dpdklab
2023-11-09 10:06 dpdklab
2023-11-09 10:06 dpdklab
2023-11-09 10:07 dpdklab
2023-11-09 10:08 dpdklab
2023-11-09 10:08 dpdklab
2023-11-09 10:09 dpdklab
2023-11-09 10:55 dpdklab
2023-11-09 10:55 dpdklab
2023-11-09 11:09 dpdklab
2023-11-09 11:09 dpdklab
2023-11-09 11:18 dpdklab
2023-11-09 11:19 dpdklab
2023-11-09 11:20 dpdklab
2023-11-09 11:21 dpdklab
2023-11-09 11:23 dpdklab
2023-11-09 11:24 dpdklab
2023-11-09 11:25 dpdklab
2023-11-09 11:26 dpdklab
2023-11-09 11:26 dpdklab
2023-11-09 11:27 dpdklab
2023-11-09 11:27 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:29 dpdklab
2023-11-09 11:32 dpdklab
2023-11-09 11:33 dpdklab
2023-11-09 11:34 dpdklab
2023-11-09 11:34 dpdklab
2023-11-09 11:35 dpdklab
2023-11-09 11:41 dpdklab
2023-11-09 11:42 dpdklab
2023-11-09 11:42 dpdklab
2023-11-09 11:50 dpdklab
2023-11-09 11:53 dpdklab
2023-11-09 11:56 dpdklab
2023-11-09 11:56 dpdklab
2023-11-09 12:01 dpdklab
2023-11-09 12:10 dpdklab
2023-11-09 12:11 dpdklab
2023-11-09 12:12 dpdklab
2023-11-09 12:13 dpdklab
2023-11-09 12:20 dpdklab
2023-11-09 12:53 dpdklab
2023-11-09 12:57 dpdklab
2023-11-09 13:50 dpdklab
2023-11-09 19:51 dpdklab
2023-11-14 0:05 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=20231109073438.D82D6120DB4@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).