automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw128192 [PATCH] maintainers: update for Reorder
Date: Tue,  6 Jun 2023 11:45:18 +0200 (CEST)	[thread overview]
Message-ID: <20230606094518.1BED512077C@dpdk.org> (raw)
In-Reply-To: <20230606094321.1865863-1-vfialko@marvell.com>

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

_coding style OK_



  parent reply	other threads:[~2023-06-06  9:45 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230606094321.1865863-1-vfialko@marvell.com>
2023-06-06  9:32 ` qemudev
2023-06-06  9:36 ` qemudev
2023-06-06  9:45 ` checkpatch [this message]
2023-06-06 10:59 ` |FAILURE| " 0-day Robot
2023-06-06 11:18 |SUCCESS| " dpdklab
2023-06-06 11:19 dpdklab
2023-06-06 11:20 dpdklab
2023-06-06 11:21 dpdklab
2023-06-06 11:22 dpdklab
2023-06-06 11:27 dpdklab
2023-06-06 11:28 dpdklab
2023-06-06 11:39 dpdklab
2023-06-06 12:22 dpdklab
2023-06-06 12:47 dpdklab
2023-06-06 13:12 dpdklab
2023-06-06 13:41 dpdklab
2023-06-06 14:08 dpdklab
2023-06-08 21:31 dpdklab
2023-06-08 21:32 dpdklab
2023-06-08 21:33 dpdklab
2023-06-08 21:34 dpdklab
2023-06-08 21:35 dpdklab
2023-06-08 21:37 dpdklab
2023-06-08 21:37 dpdklab
2023-06-08 21:37 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:38 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:39 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:40 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=20230606094518.1BED512077C@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).