From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw113230 [PATCH v4] examples/vhost: fix retry logic on eth rx path
Date: Wed, 22 Jun 2022 11:27:42 +0200 (CEST) [thread overview]
Message-ID: <20220622092742.4DF15124166@dpdk.org> (raw)
In-Reply-To: <20220622092555.1149810-1-yuanx.wang@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/113230
_coding style OK_
next parent reply other threads:[~2022-06-22 9:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220622092555.1149810-1-yuanx.wang@intel.com>
2022-06-22 9:27 ` checkpatch [this message]
2022-06-22 10:59 ` 0-day Robot
2022-06-22 9:55 |SUCCESS| pw113230 [PATCH] [v4] " dpdklab
2022-06-22 9:57 dpdklab
2022-06-22 10:04 dpdklab
2022-06-22 10:05 dpdklab
2022-06-22 10:07 dpdklab
2022-06-22 10:10 dpdklab
2022-06-22 10:14 dpdklab
2022-06-22 10:19 dpdklab
2022-06-22 10:20 dpdklab
2022-06-22 10:21 dpdklab
2022-06-22 10:21 dpdklab
2022-06-22 10:22 dpdklab
2022-06-22 10:34 dpdklab
2022-06-22 10:42 dpdklab
2022-06-22 18:54 dpdklab
2022-06-22 19:07 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=20220622092742.4DF15124166@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).