automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137092 [PATCH v1] dts: fix smoke tests driver regex
Date: Fri, 23 Feb 2024 09:30:28 +0100 (CET)	[thread overview]
Message-ID: <20240223083028.3FE04122320@dpdk.org> (raw)
In-Reply-To: <20240223083001.63167-1-juraj.linkes@pantheon.tech>

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

_coding style OK_



  parent reply	other threads:[~2024-02-23  8:30 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240223083001.63167-1-juraj.linkes@pantheon.tech>
2024-02-23  8:07 ` qemudev
2024-02-23  8:11 ` qemudev
2024-02-23  8:30 ` checkpatch [this message]
2024-02-23  9:25 ` 0-day Robot
2024-02-24  0:34 |SUCCESS| pw137092 [PATCH] [v1] " dpdklab
2024-02-24  0:39 dpdklab
2024-02-24  0:48 dpdklab
2024-02-24  0:52 dpdklab
2024-02-24  0:54 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:04 dpdklab
2024-02-24  1:15 dpdklab
2024-02-24  1:16 dpdklab
2024-02-24  1:16 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:17 dpdklab
2024-02-24  1:19 dpdklab
2024-02-24  1:33 dpdklab
2024-02-24  1:34 dpdklab
2024-02-24  1:34 dpdklab
2024-02-24  1:35 dpdklab
2024-02-24  1:36 dpdklab
2024-02-24  2:36 dpdklab
2024-02-24  2:41 dpdklab
2024-02-24  2:46 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:49 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:50 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:51 dpdklab
2024-02-24  2:52 dpdklab
2024-02-24  2:52 dpdklab
2024-02-24  2:53 dpdklab
2024-02-24  2:53 dpdklab
2024-02-24  2:54 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:57 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:58 dpdklab
2024-02-24  2:59 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  3:00 dpdklab
2024-02-24  3:03 dpdklab
2024-02-24  3:09 dpdklab
2024-02-24  3:09 dpdklab
2024-02-24  3:18 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:19 dpdklab
2024-02-24  3:20 dpdklab
2024-02-24  3:26 dpdklab
2024-02-24  3:32 dpdklab
2024-02-24  3:33 dpdklab
2024-02-24  4:02 dpdklab
2024-02-24  5:23 dpdklab
2024-02-24  9:11 dpdklab
2024-02-24 12:36 dpdklab
2024-02-24 12:55 dpdklab
2024-02-24 13:23 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=20240223083028.3FE04122320@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).