From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw152601 [PATCH v4 4/4] net/idpf: use common Tx free fn in idpf
Date: Thu, 27 Mar 2025 11:44:29 +0100 (CET) [thread overview]
Message-ID: <20250327104429.67881123E9B@dpdk.org> (raw)
In-Reply-To: <20250327104502.2107300-5-shaiq.wani@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/152601
_coding style OK_
next prev parent reply other threads:[~2025-03-27 10:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250327104502.2107300-5-shaiq.wani@intel.com>
2025-03-27 10:09 ` |SUCCESS| pw152598-152601 " qemudev
2025-03-27 10:14 ` qemudev
2025-03-27 10:44 ` checkpatch [this message]
2025-03-27 11:23 ` |PENDING| pw152598-152601 [PATCH] [v4,4/4] net/idpf: use common Tx f dpdklab
2025-03-27 11:37 ` dpdklab
2025-03-27 11:44 ` dpdklab
2025-03-27 11:44 ` |SUCCESS| " dpdklab
2025-03-27 11:46 ` dpdklab
2025-03-27 11:53 ` dpdklab
2025-03-27 12:01 ` dpdklab
2025-03-27 12:02 ` |FAILURE| pw152601 [PATCH v4 4/4] net/idpf: use common Tx free fn in idpf 0-day Robot
2025-03-27 12:05 ` |PENDING| pw152598-152601 [PATCH] [v4,4/4] net/idpf: use common Tx f dpdklab
2025-03-27 12:10 ` |WARNING| " dpdklab
2025-03-27 12:11 ` |SUCCESS| " dpdklab
2025-03-27 12:12 ` dpdklab
2025-03-27 12:16 ` dpdklab
2025-03-27 12:19 ` dpdklab
2025-03-27 12:20 ` dpdklab
2025-03-27 12:42 ` |WARNING| " dpdklab
2025-03-27 13:00 ` |SUCCESS| " dpdklab
2025-03-27 13:40 ` dpdklab
2025-03-27 13:41 ` |FAILURE| " dpdklab
2025-03-27 13:44 ` |SUCCESS| " dpdklab
2025-03-27 21:20 ` dpdklab
2025-03-27 21:43 ` dpdklab
2025-03-28 15:51 ` |PENDING| " dpdklab
2025-03-28 15:58 ` |FAILURE| " dpdklab
2025-03-28 16:15 ` |WARNING| " dpdklab
2025-03-28 16:29 ` |SUCCESS| " dpdklab
2025-03-28 16:46 ` dpdklab
2025-03-28 20:09 ` dpdklab
2025-03-29 1:21 ` 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=20250327104429.67881123E9B@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).