automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw153914 [PATCH v4 25/25] net/intel: add common Tx mbuf recycle
Date: Fri, 30 May 2025 16:03:03 +0200 (CEST)	[thread overview]
Message-ID: <20250530140303.E8049125279@dpdk.org> (raw)
In-Reply-To: <150e8c6ff6c3730f5c9ed78477d0b615c7f35a1a.1748612804.git.anatoly.burakov@intel.com>

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/153914

_coding style OK_



  parent reply	other threads:[~2025-05-30 14:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <150e8c6ff6c3730f5c9ed78477d0b615c7f35a1a.1748612804.git.anatoly.burakov@intel.com>
2025-05-30 13:28 ` |SUCCESS| pw153890-153914 " qemudev
2025-05-30 13:32 ` qemudev
2025-05-30 14:03 ` checkpatch [this message]
2025-05-30 14:53 ` |PENDING| pw153890-153914 [PATCH] [v4,25/25] net/intel: add common T dpdklab
2025-05-30 15:01 ` |FAILURE| pw153914 [PATCH v4 25/25] net/intel: add common Tx mbuf recycle 0-day Robot
2025-05-30 15:06 ` |PENDING| pw153890-153914 [PATCH] [v4,25/25] net/intel: add common T dpdklab
2025-05-30 15:07 ` |SUCCESS| " dpdklab
2025-05-30 15:25 ` |PENDING| " dpdklab
2025-05-30 15:27 ` |SUCCESS| " dpdklab
2025-05-30 15:27 ` dpdklab
2025-05-30 15:44 ` dpdklab
2025-05-30 15:44 ` dpdklab
2025-05-30 15:51 ` dpdklab
2025-05-30 16:38 ` dpdklab
2025-05-30 18:39 ` |PENDING| " dpdklab
2025-05-30 19:27 ` |WARNING| " dpdklab
2025-05-30 21:55 ` |SUCCESS| " dpdklab
2025-05-30 22:33 ` dpdklab
2025-05-30 23:59 ` |WARNING| " dpdklab
2025-05-31  0:04 ` dpdklab
2025-05-31  9:14 ` |SUCCESS| " dpdklab
2025-05-31  9:23 ` dpdklab
2025-05-31 10:41 ` dpdklab
2025-06-04 16:42 ` dpdklab
2025-06-10 20:00 ` dpdklab
2025-06-10 20:00 ` 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=20250530140303.E8049125279@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).