From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw121577 [PATCH 1/3] cryptodev: add SHAKE algorithm
Date: Wed, 4 Jan 2023 15:40:13 +0100 (CET) [thread overview]
Message-ID: <20230104144013.A7432122EC0@dpdk.org> (raw)
In-Reply-To: <20230104143815.603524-2-vfialko@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/121577
_coding style OK_
next parent reply other threads:[~2023-01-04 14:40 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230104143815.603524-2-vfialko@marvell.com>
2023-01-04 14:40 ` checkpatch [this message]
2023-01-04 14:41 ` |WARNING| pw121577-121579 " qemudev
2023-01-04 14:41 ` qemudev
2023-01-04 14:51 ` qemudev
2023-01-04 15:00 ` qemudev
2023-01-04 15:00 ` qemudev
2023-01-04 15:16 ` qemudev
2023-01-04 15:20 ` qemudev
2023-01-04 15:30 ` qemudev
2023-01-04 15:35 ` qemudev
2023-01-04 15:35 ` qemudev
2023-01-04 15:45 ` qemudev
2023-01-04 16:30 ` qemudev
2023-01-04 16:40 ` qemudev
2023-01-04 16:50 ` qemudev
2023-01-04 16:50 ` qemudev
2023-01-04 16:55 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:05 ` qemudev
2023-01-04 17:05 ` qemudev
2023-01-04 17:10 ` qemudev
2023-01-04 17:10 ` qemudev
2023-01-04 17:15 ` qemudev
2023-01-04 17:20 ` qemudev
2023-01-04 17:25 ` qemudev
2023-01-04 17:25 ` qemudev
2023-01-04 17:30 ` qemudev
2023-01-04 17:35 ` qemudev
2023-01-04 17:35 ` qemudev
2023-01-04 17:40 ` qemudev
2023-01-04 17:45 ` qemudev
2023-01-04 17:45 ` qemudev
2023-01-04 17:50 ` qemudev
2023-01-04 17:55 ` qemudev
2023-01-04 18:00 ` qemudev
2023-01-04 18:00 ` qemudev
2023-01-04 18:05 ` qemudev
2023-01-04 18:05 ` qemudev
2023-01-04 18:30 ` qemudev
2023-01-04 18:30 ` qemudev
2023-01-04 18:35 ` qemudev
2023-01-04 18:50 ` qemudev
2023-01-04 18:55 ` qemudev
2023-01-04 18:55 ` qemudev
2023-01-04 19:05 ` qemudev
2023-01-04 19:05 ` qemudev
2023-01-04 19:10 ` qemudev
2023-01-04 19:10 ` qemudev
2023-01-04 19:25 ` qemudev
2023-01-04 19:30 ` qemudev
2023-01-04 19:30 ` qemudev
2023-01-04 19:50 ` qemudev
2023-01-04 19:55 ` qemudev
2023-01-04 20:10 ` qemudev
2023-01-04 20:20 ` qemudev
2023-01-04 20:25 ` qemudev
2023-01-04 20:25 ` qemudev
2023-01-04 20:35 ` qemudev
2023-01-04 20:42 ` qemudev
2023-01-04 20:55 ` qemudev
2023-01-04 21:00 ` qemudev
2023-01-04 21:45 ` qemudev
2023-01-04 21:50 ` qemudev
2023-01-04 21:55 ` qemudev
2023-01-04 21:55 ` qemudev
2023-01-04 22:10 ` qemudev
2023-01-04 22:10 ` qemudev
2023-01-04 22:20 ` qemudev
2023-01-04 22:20 ` qemudev
2023-01-04 23:05 ` qemudev
2023-01-04 23:05 ` qemudev
2023-01-04 23:15 ` qemudev
2023-01-04 23:15 ` qemudev
2023-01-04 23:45 ` qemudev
2023-01-05 0:05 ` qemudev
2023-01-05 0:15 ` qemudev
2023-01-05 0:20 ` qemudev
2023-01-05 0:25 ` qemudev
2023-01-05 0:25 ` qemudev
2023-01-05 0:30 ` qemudev
2023-01-05 0:50 ` qemudev
2023-01-05 0:50 ` qemudev
2023-01-05 1:05 ` qemudev
2023-01-05 1:20 ` qemudev
2023-01-05 1:30 ` qemudev
2023-01-05 1:35 ` qemudev
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=20230104144013.A7432122EC0@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).