automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141229 [PATCH v2 3/3] dts: queue suite conf schema
Date: Mon, 17 Jun 2024 21:49:16 +0200 (CEST)	[thread overview]
Message-ID: <20240617194916.0C80F124124@dpdk.org> (raw)
In-Reply-To: <20240617194638.12926-8-dmarx@iol.unh.edu>

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

_coding style OK_



  parent reply	other threads:[~2024-06-17 19:49 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240617194638.12926-8-dmarx@iol.unh.edu>
2024-06-17 19:22 ` |SUCCESS| pw141227-141229 " qemudev
2024-06-17 19:27 ` qemudev
2024-06-17 19:49 ` checkpatch [this message]
2024-06-17 20:44 ` |SUCCESS| pw141229 " 0-day Robot
2024-06-17 21:39 ` |SUCCESS| pw141227-141229 [PATCH] [v2,3/3] dts: queue suite conf sch dpdklab
2024-06-17 21:48 ` dpdklab
2024-06-17 21:51 ` |FAILURE| " dpdklab
2024-06-17 22:01 ` |SUCCESS| " dpdklab
2024-06-17 22:02 ` |FAILURE| " dpdklab
2024-06-17 22:06 ` |SUCCESS| " dpdklab
2024-06-17 22:18 ` dpdklab
2024-06-17 22:30 ` dpdklab
2024-06-17 22:31 ` dpdklab
2024-06-17 22:31 ` dpdklab
2024-06-17 22:32 ` dpdklab
2024-06-17 22:32 ` dpdklab
2024-06-17 22:33 ` dpdklab
2024-06-17 22:36 ` dpdklab
2024-06-17 22:36 ` dpdklab
2024-06-17 22:37 ` dpdklab
2024-06-17 22:38 ` dpdklab
2024-06-17 22:40 ` dpdklab
2024-06-17 22:40 ` dpdklab
2024-06-17 22:42 ` dpdklab
2024-06-17 22:45 ` |FAILURE| " dpdklab
2024-06-17 22:55 ` |SUCCESS| " dpdklab
2024-06-17 22:55 ` dpdklab
2024-06-17 22:56 ` dpdklab
2024-06-17 23:05 ` dpdklab
2024-06-17 23:07 ` dpdklab
2024-06-17 23:08 ` dpdklab
2024-06-17 23:11 ` dpdklab
2024-06-17 23:18 ` dpdklab
2024-06-17 23:21 ` dpdklab
2024-06-17 23:30 ` dpdklab
2024-06-18  0:21 ` dpdklab
2024-06-18  0:22 ` dpdklab
2024-06-18  0:30 ` dpdklab
2024-06-18  0:30 ` dpdklab
2024-06-18  0:32 ` dpdklab
2024-06-18  0:33 ` dpdklab
2024-06-18  0:33 ` dpdklab
2024-06-18  0:34 ` dpdklab
2024-06-18  0:35 ` dpdklab
2024-06-18  0:35 ` dpdklab
2024-06-18  0:35 ` dpdklab
2024-06-18  0:35 ` dpdklab
2024-06-18  0:36 ` dpdklab
2024-06-18  0:38 ` dpdklab
2024-06-18  0:39 ` dpdklab
2024-06-18  0:40 ` dpdklab
2024-06-18  0:43 ` dpdklab
2024-06-18  0:44 ` dpdklab
2024-06-18  0:45 ` dpdklab
2024-06-18  0:45 ` dpdklab
2024-06-18  0:46 ` dpdklab
2024-06-18  0:46 ` dpdklab
2024-06-18  0:47 ` dpdklab
2024-06-18  0:47 ` dpdklab
2024-06-18  0:47 ` dpdklab
2024-06-18  0:48 ` dpdklab
2024-06-18  0:48 ` dpdklab
2024-06-18  0:51 ` dpdklab
2024-06-18  0:52 ` dpdklab
2024-06-18  0:54 ` dpdklab
2024-06-18  0:54 ` dpdklab
2024-06-18  0:55 ` dpdklab
2024-06-18  0:56 ` dpdklab
2024-06-18  1:05 ` dpdklab
2024-06-18  1:06 ` dpdklab
2024-06-18  1:07 ` dpdklab
2024-06-18  1:07 ` dpdklab
2024-06-18  1:08 ` dpdklab
2024-06-18  1:08 ` dpdklab
2024-06-18  1:08 ` dpdklab
2024-06-18  1:09 ` dpdklab
2024-06-18  1:10 ` dpdklab
2024-06-18  1:20 ` dpdklab
2024-06-18  1:23 ` dpdklab
2024-06-18  1:23 ` dpdklab
2024-06-18  1:23 ` dpdklab
2024-06-18  1:26 ` dpdklab
2024-06-18  1:26 ` dpdklab
2024-06-18  1:27 ` dpdklab
2024-06-18  1:28 ` dpdklab
2024-06-18  1:29 ` dpdklab
2024-06-18  1:29 ` dpdklab
2024-06-18  1:31 ` dpdklab
2024-06-18  1:33 ` dpdklab
2024-06-18  1:34 ` dpdklab
2024-06-18  1:34 ` dpdklab
2024-06-18  1:34 ` dpdklab
2024-06-18  1:35 ` dpdklab
2024-06-18  1:36 ` dpdklab
2024-06-18  1:36 ` dpdklab
2024-06-18  1:36 ` dpdklab
2024-06-18  1:37 ` dpdklab
2024-06-18  1:37 ` dpdklab
2024-06-18  1:40 ` dpdklab
2024-06-18  1:41 ` dpdklab
2024-06-18  2:03 ` dpdklab
2024-06-18  2:05 ` dpdklab
2024-06-18  2:14 ` dpdklab
2024-06-18  2:20 ` dpdklab
2024-06-18  2:21 ` dpdklab
2024-06-18  2:21 ` dpdklab
2024-06-18  2:54 ` dpdklab
2024-06-18  3:21 ` dpdklab
2024-06-18  3:37 ` dpdklab
2024-06-18  5:18 ` 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=20240617194916.0C80F124124@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).