From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw106150 [PATCH] crypto/ipsec_mb: fix buffer overrun
Date: Thu, 20 Jan 2022 18:06:53 +0100 (CET) [thread overview]
Message-ID: <20220120170653.70B9D12091F@dpdk.org> (raw)
In-Reply-To: <20220120170455.41407-1-pablo.de.lara.guarch@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/106150
_coding style OK_
next parent reply other threads:[~2022-01-20 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220120170455.41407-1-pablo.de.lara.guarch@intel.com>
2022-01-20 17:06 ` checkpatch [this message]
2022-01-20 19:00 ` 0-day Robot
2022-01-20 17:27 dpdklab
2022-01-20 17:32 dpdklab
2022-01-20 17:35 dpdklab
2022-01-20 17:36 dpdklab
2022-01-20 17:39 dpdklab
2022-01-20 17:39 dpdklab
2022-01-20 17:40 dpdklab
2022-01-20 17:40 dpdklab
2022-01-20 17:44 dpdklab
2022-01-20 19:04 dpdklab
2022-01-20 19:23 dpdklab
2022-01-20 20:25 dpdklab
2022-01-20 22:37 dpdklab
2022-01-21 8:43 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=20220120170653.70B9D12091F@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).