From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139281 [PATCH] crypto: fix crypto callbacks macro
Date: Mon, 15 Apr 2024 14:36:27 +0200 (CEST) [thread overview]
Message-ID: <20240415123627.8E2B812083E@dpdk.org> (raw)
In-Reply-To: <20240415123548.705412-1-ciara.power@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139281
_coding style OK_
next prev parent reply other threads:[~2024-04-15 12:36 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240415123548.705412-1-ciara.power@intel.com>
2024-04-15 12:13 ` qemudev
2024-04-15 12:17 ` qemudev
2024-04-15 12:36 ` checkpatch [this message]
2024-04-15 13:23 ` 0-day Robot
2024-04-15 21:40 ` dpdklab
2024-04-15 21:45 ` dpdklab
2024-04-15 21:46 ` dpdklab
2024-04-15 21:46 ` dpdklab
2024-04-15 21:47 ` dpdklab
2024-04-15 21:48 ` dpdklab
2024-04-15 21:49 ` dpdklab
2024-04-15 22:05 ` dpdklab
2024-04-15 22:14 ` dpdklab
2024-04-15 22:15 ` dpdklab
2024-04-15 22:17 ` dpdklab
2024-04-15 22:17 ` dpdklab
2024-04-15 22:18 ` dpdklab
2024-04-15 22:19 ` dpdklab
2024-04-15 22:19 ` dpdklab
2024-04-15 22:19 ` dpdklab
2024-04-15 22:19 ` dpdklab
2024-04-15 22:19 ` dpdklab
2024-04-15 22:20 ` dpdklab
2024-04-15 22:20 ` dpdklab
2024-04-15 22:20 ` dpdklab
2024-04-15 22:20 ` dpdklab
2024-04-15 22:20 ` dpdklab
2024-04-15 22:21 ` dpdklab
2024-04-15 22:22 ` dpdklab
2024-04-15 22:22 ` dpdklab
2024-04-15 22:22 ` dpdklab
2024-04-15 22:22 ` dpdklab
2024-04-15 22:23 ` dpdklab
2024-04-15 22:23 ` dpdklab
2024-04-15 22:23 ` dpdklab
2024-04-15 22:23 ` dpdklab
2024-04-15 22:23 ` dpdklab
2024-04-15 22:24 ` dpdklab
2024-04-15 22:24 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:25 ` dpdklab
2024-04-15 22:26 ` dpdklab
2024-04-15 22:26 ` dpdklab
2024-04-15 22:26 ` dpdklab
2024-04-15 22:26 ` dpdklab
2024-04-15 22:26 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:27 ` dpdklab
2024-04-15 22:28 ` dpdklab
2024-04-15 22:28 ` dpdklab
2024-04-15 22:28 ` dpdklab
2024-04-15 22:28 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:29 ` dpdklab
2024-04-15 22:30 ` dpdklab
2024-04-15 22:31 ` dpdklab
2024-04-15 22:32 ` dpdklab
2024-04-15 22:33 ` dpdklab
2024-04-15 22:34 ` dpdklab
2024-04-15 22:36 ` dpdklab
2024-04-15 22:37 ` dpdklab
2024-04-15 22:40 ` dpdklab
2024-04-15 22:43 ` dpdklab
2024-04-15 22:47 ` dpdklab
2024-04-15 22:49 ` dpdklab
2024-04-15 22:50 ` dpdklab
2024-04-15 22:54 ` dpdklab
2024-04-15 22:59 ` dpdklab
2024-04-15 23:01 ` dpdklab
2024-04-15 23:01 ` dpdklab
2024-04-15 23:21 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:31 ` dpdklab
2024-04-16 1:19 ` 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=20240415123627.8E2B812083E@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).