automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142112 [PATCH v5 3/3] dts: queue suite conf schema
Date: Wed,  3 Jul 2024 20:09:38 +0200 (CEST)	[thread overview]
Message-ID: <20240703180938.5440A128144@dpdk.org> (raw)
In-Reply-To: <20240703180820.18723-3-dmarx@iol.unh.edu>

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

_coding style OK_



  parent reply	other threads:[~2024-07-03 18:09 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703180820.18723-3-dmarx@iol.unh.edu>
2024-07-03 17:43 ` |SUCCESS| pw142110-142112 " qemudev
2024-07-03 17:47 ` qemudev
2024-07-03 18:09 ` checkpatch [this message]
2024-07-03 19:04 ` |SUCCESS| pw142112 " 0-day Robot
2024-07-03 21:21 ` |SUCCESS| pw142110-142112 [PATCH] [v5,3/3] dts: queue suite conf sch dpdklab
2024-07-03 21:21 ` dpdklab
2024-07-03 21:26 ` dpdklab
2024-07-03 21:30 ` dpdklab
2024-07-03 21:39 ` dpdklab
2024-07-03 21:50 ` dpdklab
2024-07-03 21:53 ` dpdklab
2024-07-03 22:12 ` |PENDING| " dpdklab
2024-07-03 22:12 ` dpdklab
2024-07-03 22:12 ` dpdklab
2024-07-03 22:13 ` dpdklab
2024-07-03 22:15 ` dpdklab
2024-07-03 22:17 ` dpdklab
2024-07-03 22:17 ` dpdklab
2024-07-03 22:17 ` |SUCCESS| " dpdklab
2024-07-03 22:18 ` |PENDING| " dpdklab
2024-07-03 22:18 ` dpdklab
2024-07-03 22:19 ` dpdklab
2024-07-03 22:24 ` dpdklab
2024-07-03 22:32 ` dpdklab
2024-07-03 22:44 ` |SUCCESS| " dpdklab
2024-07-03 22:53 ` dpdklab
2024-07-04  1:11 ` |PENDING| " dpdklab
2024-07-04  1:15 ` |SUCCESS| " dpdklab
2024-07-04  1:16 ` dpdklab
2024-07-04  1:17 ` dpdklab
2024-07-04  1:17 ` dpdklab
2024-07-04  2:14 ` |PENDING| " dpdklab
2024-07-04  2:15 ` dpdklab
2024-07-04  2:17 ` dpdklab
2024-07-04  2:20 ` dpdklab
2024-07-04  2:27 ` dpdklab
2024-07-04  2:29 ` dpdklab
2024-07-04  2:34 ` dpdklab
2024-07-04  2:35 ` dpdklab
2024-07-04  2:37 ` dpdklab
2024-07-04  2:44 ` dpdklab
2024-07-04  2:48 ` dpdklab
2024-07-04  2:50 ` dpdklab
2024-07-04  2:51 ` dpdklab
2024-07-04  2:56 ` dpdklab
2024-07-04  3:00 ` dpdklab
2024-07-04  3:02 ` dpdklab
2024-07-04  3:04 ` dpdklab
2024-07-04  3:04 ` dpdklab
2024-07-04  3:11 ` dpdklab
2024-07-04  3:19 ` dpdklab
2024-07-04  3:19 ` dpdklab
2024-07-04  3:20 ` dpdklab
2024-07-04  3:21 ` dpdklab
2024-07-04  3:23 ` dpdklab
2024-07-04  3:26 ` dpdklab
2024-07-04  3:27 ` dpdklab
2024-07-04  3:30 ` dpdklab
2024-07-04  3:30 ` |SUCCESS| " dpdklab
2024-07-04  3:33 ` |PENDING| " dpdklab
2024-07-04  3:35 ` dpdklab
2024-07-04  3:41 ` dpdklab
2024-07-04  3:42 ` dpdklab
2024-07-04  3:47 ` dpdklab
2024-07-04  3:47 ` dpdklab
2024-07-04  3:48 ` dpdklab
2024-07-04  3:48 ` dpdklab
2024-07-04  3:52 ` dpdklab
2024-07-04  3:56 ` dpdklab
2024-07-04  3:57 ` dpdklab
2024-07-04  4:03 ` dpdklab
2024-07-04  4:04 ` |SUCCESS| " dpdklab
2024-07-04  4:07 ` |PENDING| " dpdklab
2024-07-04  4:07 ` |SUCCESS| " dpdklab
2024-07-04  4:11 ` |PENDING| " dpdklab
2024-07-04  4:17 ` dpdklab
2024-07-04  4:19 ` dpdklab
2024-07-04  4:20 ` dpdklab
2024-07-04  4:26 ` dpdklab
2024-07-04  4:31 ` |SUCCESS| " dpdklab
2024-07-04  4:33 ` |PENDING| " dpdklab
2024-07-04  5:31 ` dpdklab
2024-07-04  5:44 ` dpdklab
2024-07-04  5:48 ` dpdklab
2024-07-04  6:03 ` dpdklab
2024-07-04  6:05 ` dpdklab
2024-07-04  6:09 ` dpdklab
2024-07-04  6:11 ` dpdklab
2024-07-04  6:12 ` dpdklab
2024-07-04  6:22 ` dpdklab
2024-07-04  6:23 ` dpdklab
2024-07-04  6:30 ` dpdklab
2024-07-04  6:37 ` dpdklab
2024-07-04  6:39 ` dpdklab
2024-07-04  6:46 ` |SUCCESS| " dpdklab
2024-07-04  6:51 ` |PENDING| " dpdklab
2024-07-04  6:56 ` dpdklab
2024-07-04  7:10 ` dpdklab
2024-07-04  7:17 ` dpdklab
2024-07-04  7:26 ` dpdklab
2024-07-04  7:40 ` dpdklab
2024-07-04  7:58 ` dpdklab
2024-07-04  8:15 ` dpdklab
2024-07-04  8:22 ` dpdklab
2024-07-04  8:37 ` |SUCCESS| " dpdklab
2024-07-05  1:44 ` dpdklab
2024-07-05  2:20 ` 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=20240703180938.5440A128144@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).