From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw104619 [PATCH] app/testpmd: fix scheduling send burst interval
Date: Tue, 23 Nov 2021 17:33:29 +0100 (CET) [thread overview]
Message-ID: <20211123163329.BA2F3121E6B@dpdk.org> (raw)
In-Reply-To: <20211123163258.14972-1-viacheslavo@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/104619
_coding style OK_
next parent reply other threads:[~2021-11-23 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211123163258.14972-1-viacheslavo@nvidia.com>
2021-11-23 16:33 ` checkpatch [this message]
2021-11-23 17:18 ` 0-day Robot
2021-11-23 17:34 dpdklab
2021-11-23 17:48 dpdklab
2021-11-23 17:51 dpdklab
2021-11-23 17:57 dpdklab
2021-11-23 17:58 dpdklab
2021-11-23 17:59 dpdklab
2021-11-23 18:03 dpdklab
2021-11-23 18:09 dpdklab
2021-11-23 18:13 dpdklab
2021-11-23 18:26 dpdklab
2021-11-23 18:31 dpdklab
2021-11-23 18:43 dpdklab
2021-11-23 19:12 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=20211123163329.BA2F3121E6B@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).