automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138577 [PATCH] graph: enhance export to graphviz
Date: Wed, 20 Mar 2024 18:12:09 +0100 (CET)	[thread overview]
Message-ID: <20240320171209.5B6771223F9@dpdk.org> (raw)
In-Reply-To: <20240320171120.255142-2-rjarry@redhat.com>

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

_coding style OK_



  parent reply	other threads:[~2024-03-20 17:12 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320171120.255142-2-rjarry@redhat.com>
2024-03-20 16:50 ` qemudev
2024-03-20 16:54 ` qemudev
2024-03-20 17:12 ` checkpatch [this message]
2024-03-20 18:04 ` |FAILURE| " 0-day Robot
2024-03-20 18:38 ` |SUCCESS| " dpdklab
2024-03-20 18:42 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:44 ` dpdklab
2024-03-20 18:45 ` dpdklab
2024-03-20 18:45 ` dpdklab
2024-03-20 18:46 ` dpdklab
2024-03-20 18:46 ` dpdklab
2024-03-20 18:47 ` dpdklab
2024-03-20 18:47 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:48 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:49 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-20 18:51 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:58 ` dpdklab
2024-03-20 18:59 ` dpdklab
2024-03-20 18:59 ` dpdklab
2024-03-20 19:00 ` dpdklab
2024-03-20 19:01 ` dpdklab
2024-03-20 19:15 ` dpdklab
2024-03-20 19:15 ` dpdklab
2024-03-20 19:16 ` dpdklab
2024-03-20 19:17 ` dpdklab
2024-03-20 19:18 ` dpdklab
2024-03-20 19:30 ` dpdklab
2024-03-20 19:36 ` dpdklab
2024-03-20 20:09 ` dpdklab
2024-03-21 13:25 ` dpdklab
2024-03-22  7:11 ` dpdklab
2024-03-22  7:50 ` 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=20240320171209.5B6771223F9@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).