From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw113672 [PATCH] app/regex: fix mbuf size for multi segemnt buffers
Date: Tue, 5 Jul 2022 10:11:36 +0200 (CEST) [thread overview]
Message-ID: <20220705081136.76D181209CE@dpdk.org> (raw)
In-Reply-To: <20220705080917.13784-1-rasland@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/113672
_coding style OK_
next parent reply other threads:[~2022-07-05 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220705080917.13784-1-rasland@nvidia.com>
2022-07-05 8:11 ` checkpatch [this message]
2022-07-05 9:18 ` 0-day Robot
2022-07-05 14:52 dpdklab
2022-07-05 14:59 dpdklab
2022-07-05 15:48 dpdklab
2022-07-05 16:09 dpdklab
2022-07-05 16:15 dpdklab
2022-07-05 16:31 dpdklab
2022-07-05 16:39 dpdklab
2022-07-05 16:39 dpdklab
2022-07-05 16:46 dpdklab
2022-07-05 17:06 dpdklab
2022-07-05 17:14 dpdklab
2022-07-05 17:30 dpdklab
2022-07-05 17:36 dpdklab
2022-07-05 17:56 dpdklab
2022-07-05 21:02 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=20220705081136.76D181209CE@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).