From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw124591 [v2, 10/10] examples/fips_validation: add extra space in JSON buffer
Date: Tue, 28 Feb 2023 18:30:43 +0100 (CET) [thread overview]
Message-ID: <20230228173043.8A016120D89@dpdk.org> (raw)
In-Reply-To: <dd772a69f039466c5b33ad82f0fba233eb9a08cf.1677604524.git.gmuthukrishn@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/124591
_coding style OK_
next parent reply other threads:[~2023-02-28 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd772a69f039466c5b33ad82f0fba233eb9a08cf.1677604524.git.gmuthukrishn@marvell.com>
2023-02-28 17:30 ` checkpatch [this message]
2023-02-28 19:19 ` 0-day Robot
2023-03-01 8:11 ` |SUCCESS| pw124581-124591 " qemudev
2023-03-01 8:12 ` 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=20230228173043.8A016120D89@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).