From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw115695 [dpdk-dev v2] crypto/openssl: fix HMAC output length
Date: Wed, 31 Aug 2022 17:10:06 +0200 (CEST) [thread overview]
Message-ID: <20220831151006.A5384121F02@dpdk.org> (raw)
In-Reply-To: <20220831150918.86824-1-kai.ji@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/115695
_coding style OK_
next parent reply other threads:[~2022-08-31 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220831150918.86824-1-kai.ji@intel.com>
2022-08-31 15:10 ` checkpatch [this message]
2022-08-31 16:59 ` 0-day Robot
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=20220831151006.A5384121F02@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).