automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140926 [PATCH v15 6/6] test: add unit test for ptr compression
Date: Tue, 11 Jun 2024 15:01:40 +0200 (CEST)	[thread overview]
Message-ID: <20240611130140.C7029124124@dpdk.org> (raw)
In-Reply-To: <20240611125947.511243-7-paul.szczepanek@arm.com>

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

_coding style OK_



  parent reply	other threads:[~2024-06-11 13:01 UTC|newest]

Thread overview: 108+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240611125947.511243-7-paul.szczepanek@arm.com>
2024-06-11 12:45 ` |SUCCESS| pw140921-140926 " qemudev
2024-06-11 12:49 ` qemudev
2024-06-11 13:01 ` checkpatch [this message]
2024-06-11 13:53 ` |SUCCESS| pw140921-140926 [PATCH] [v15,6/6] test: add unit test for dpdklab
2024-06-11 14:01 ` dpdklab
2024-06-11 14:01 ` dpdklab
2024-06-11 14:03 ` dpdklab
2024-06-11 14:03 ` |SUCCESS| pw140926 [PATCH v15 6/6] test: add unit test for ptr compression 0-day Robot
2024-06-11 14:15 ` |SUCCESS| pw140921-140926 [PATCH] [v15,6/6] test: add unit test for dpdklab
2024-06-11 14:17 ` dpdklab
2024-06-13  0:36 ` dpdklab
2024-06-13  0:36 ` dpdklab
2024-06-13  0:36 ` dpdklab
2024-06-13  0:36 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:37 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:38 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:39 ` dpdklab
2024-06-13  0:40 ` dpdklab
2024-06-13  0:40 ` dpdklab
2024-06-13  0:40 ` dpdklab
2024-06-13  0:40 ` dpdklab
2024-06-13  0:40 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:41 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:42 ` dpdklab
2024-06-13  0:43 ` dpdklab
2024-06-13  0:43 ` dpdklab
2024-06-13  0:43 ` dpdklab
2024-06-13  0:43 ` dpdklab
2024-06-13  0:44 ` dpdklab
2024-06-13  0:44 ` dpdklab
2024-06-13  0:44 ` dpdklab
2024-06-13  0:44 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:45 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:46 ` dpdklab
2024-06-13  0:47 ` dpdklab
2024-06-13  0:47 ` dpdklab
2024-06-13  0:47 ` dpdklab
2024-06-13  0:47 ` dpdklab
2024-06-13  0:48 ` dpdklab
2024-06-13  0:48 ` dpdklab
2024-06-13  0:48 ` dpdklab
2024-06-13  0:49 ` dpdklab
2024-06-13  0:54 ` dpdklab
2024-06-13  0:55 ` dpdklab
2024-06-13  0:57 ` dpdklab
2024-06-13  0:58 ` dpdklab
2024-06-13  0:59 ` dpdklab
2024-06-13  0:59 ` dpdklab
2024-06-13  1:00 ` dpdklab
2024-06-13  1:02 ` dpdklab
2024-06-13  1:02 ` dpdklab
2024-06-13  1:04 ` dpdklab
2024-06-13  1:08 ` dpdklab
2024-06-13  1:09 ` 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=20240611130140.C7029124124@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).