From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138478 [PATCH] net/nfp: fix representor port release queue problem
Date: Tue, 19 Mar 2024 08:08:41 +0100 (CET) [thread overview]
Message-ID: <20240319070841.7EF1E1223F7@dpdk.org> (raw)
In-Reply-To: <20240319070754.398799-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138478
_coding style OK_
next prev parent reply other threads:[~2024-03-19 7:08 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319070754.398799-1-chaoyong.he@corigine.com>
2024-03-19 6:47 ` qemudev
2024-03-19 6:52 ` qemudev
2024-03-19 7:08 ` checkpatch [this message]
2024-03-19 8:03 ` 0-day Robot
2024-03-19 19:41 ` |SUCCESS| pw138478 [PATCH] net/nfp: fix representor port release que dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:46 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:13 ` dpdklab
2024-03-19 20:15 ` dpdklab
2024-03-19 20:15 ` dpdklab
2024-03-19 20:22 ` dpdklab
2024-03-19 20:22 ` dpdklab
2024-03-19 20:22 ` dpdklab
2024-03-19 20:31 ` dpdklab
2024-03-19 20:35 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:56 ` dpdklab
2024-03-19 21:00 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-19 21:08 ` dpdklab
2024-03-19 21:08 ` dpdklab
2024-03-19 21:08 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:09 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:10 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:11 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:12 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:13 ` dpdklab
2024-03-19 21:14 ` dpdklab
2024-03-19 21:14 ` dpdklab
2024-03-19 21:14 ` dpdklab
2024-03-19 21:14 ` dpdklab
2024-03-19 21:14 ` dpdklab
2024-03-19 21:27 ` dpdklab
2024-03-19 21:51 ` dpdklab
2024-03-19 22:26 ` dpdklab
2024-03-19 22:37 ` dpdklab
2024-03-19 22:50 ` dpdklab
2024-03-19 23:46 ` dpdklab
2024-03-20 19:58 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 13:15 ` 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=20240319070841.7EF1E1223F7@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).