From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw112671 [PATCH] test/crypto: fix warnings for optimization=1 build
Date: Sat, 11 Jun 2022 00:09:56 +0200 (CEST) [thread overview]
Message-ID: <20220610220956.C91E9123450@dpdk.org> (raw)
In-Reply-To: <872fbb13ed0df67f7dedbf3db340464bb7391af1.1654898453.git.rahul.lakkireddy@chelsio.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/112671
_coding style OK_
next parent reply other threads:[~2022-06-10 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <872fbb13ed0df67f7dedbf3db340464bb7391af1.1654898453.git.rahul.lakkireddy@chelsio.com>
2022-06-10 22:09 ` checkpatch [this message]
2022-06-10 23:19 ` 0-day Robot
2022-06-10 22:42 dpdklab
2022-06-10 22:44 dpdklab
2022-06-10 22:48 dpdklab
2022-06-10 22:57 dpdklab
2022-06-10 23:48 dpdklab
2022-06-11 0:07 dpdklab
2022-06-11 0:14 dpdklab
2022-06-11 4:19 dpdklab
2022-06-11 4:24 dpdklab
2022-06-11 5:10 dpdklab
2022-06-13 1:48 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=20220610220956.C91E9123450@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).