From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw84445 [PATCH] net/mlx5: fix mbufs overflow in vectorized MPRQ
Date: Sat, 21 Nov 2020 04:43:19 +0100 (CET) [thread overview]
Message-ID: <20201121034319.A558CC8D8@dpdk.org> (raw)
In-Reply-To: <20201121034239.13404-1-akozyrev@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/84445
_coding style OK_
next parent reply other threads:[~2020-11-21 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201121034239.13404-1-akozyrev@nvidia.com>
2020-11-21 3:43 ` checkpatch [this message]
2020-12-11 17:00 ` [dpdk-test-report] |SUCCESS| pw84445 " 0-day Robot
2020-11-21 8:52 [dpdk-test-report] |SUCCESS| pw84445 [PATCH] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2020-11-21 4:49 dpdklab
2020-11-21 4:39 dpdklab
2020-11-21 4:31 dpdklab
2020-11-21 4:25 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=20201121034319.A558CC8D8@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).