automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140136 [PATCH v4 8/8] net/null: use generic SW stats
Date: Thu, 16 May 2024 01:44:13 +0200 (CEST)	[thread overview]
Message-ID: <20240515234413.2799E121E57@dpdk.org> (raw)
In-Reply-To: <20240515234234.5015-9-stephen@networkplumber.org>

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

_coding style OK_



  parent reply	other threads:[~2024-05-15 23:44 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240515234234.5015-9-stephen@networkplumber.org>
2024-05-15 23:17 ` |SUCCESS| pw140129-140136 " qemudev
2024-05-15 23:22 ` qemudev
2024-05-15 23:44 ` checkpatch [this message]
2024-05-16  0:38 ` |SUCCESS| pw140129-140136 [PATCH] [v4,8/8] net/null: use generic SW dpdklab
2024-05-16  0:39 ` dpdklab
2024-05-16  0:39 ` dpdklab
2024-05-16  0:40 ` |FAILURE| " dpdklab
2024-05-16  0:40 ` |SUCCESS| " dpdklab
2024-05-16  0:41 ` |FAILURE| " dpdklab
2024-05-16  0:42 ` |SUCCESS| " dpdklab
2024-05-16  0:43 ` |FAILURE| " dpdklab
2024-05-16  0:43 ` dpdklab
2024-05-16  0:44 ` |SUCCESS| " dpdklab
2024-05-16  0:44 ` |FAILURE| pw140136 [PATCH v4 8/8] net/null: use generic SW stats 0-day Robot
2024-05-16  0:45 ` |SUCCESS| pw140129-140136 [PATCH] [v4,8/8] net/null: use generic SW dpdklab
2024-05-16  0:45 ` dpdklab
2024-05-16  0:45 ` |FAILURE| " dpdklab
2024-05-16  0:46 ` dpdklab
2024-05-16  0:46 ` dpdklab
2024-05-16  0:47 ` dpdklab
2024-05-16  0:47 ` dpdklab
2024-05-16  0:48 ` dpdklab
2024-05-16  0:48 ` |SUCCESS| " dpdklab
2024-05-16  0:48 ` |FAILURE| " dpdklab
2024-05-16  0:49 ` |SUCCESS| " dpdklab
2024-05-16  0:49 ` dpdklab
2024-05-16  0:50 ` |FAILURE| " dpdklab
2024-05-16  0:50 ` |SUCCESS| " dpdklab
2024-05-16  0:51 ` |FAILURE| " dpdklab
2024-05-16  0:52 ` dpdklab
2024-05-16  0:52 ` |SUCCESS| " dpdklab
2024-05-16  0:53 ` dpdklab
2024-05-16  0:53 ` dpdklab
2024-05-16  0:55 ` dpdklab
2024-05-16  0:55 ` dpdklab
2024-05-16  0:56 ` dpdklab
2024-05-16  0:57 ` |FAILURE| " dpdklab
2024-05-16  0:57 ` dpdklab
2024-05-16  0:57 ` |SUCCESS| " dpdklab
2024-05-16  0:57 ` dpdklab
2024-05-16  0:58 ` |FAILURE| " dpdklab
2024-05-16  0:58 ` |SUCCESS| " dpdklab
2024-05-16  0:58 ` |FAILURE| " dpdklab
2024-05-16  0:58 ` |SUCCESS| " dpdklab
2024-05-16  0:58 ` |FAILURE| " dpdklab
2024-05-16  0:59 ` |SUCCESS| " dpdklab
2024-05-16  0:59 ` dpdklab
2024-05-16  0:59 ` |FAILURE| " dpdklab
2024-05-16  0:59 ` |SUCCESS| " dpdklab
2024-05-16  0:59 ` dpdklab
2024-05-16  1:00 ` |FAILURE| " dpdklab
2024-05-16  1:00 ` |SUCCESS| " dpdklab
2024-05-16  1:00 ` |FAILURE| " dpdklab
2024-05-16  1:00 ` |SUCCESS| " dpdklab
2024-05-16  1:00 ` dpdklab
2024-05-16  1:00 ` dpdklab
2024-05-16  1:01 ` dpdklab
2024-05-16  1:01 ` dpdklab
2024-05-16  1:01 ` dpdklab
2024-05-16  1:01 ` dpdklab
2024-05-16  1:02 ` |FAILURE| " dpdklab
2024-05-16  1:02 ` |SUCCESS| " dpdklab
2024-05-16  1:02 ` dpdklab
2024-05-16  1:02 ` |FAILURE| " dpdklab
2024-05-16  1:10 ` |SUCCESS| " dpdklab
2024-05-16  1:10 ` |FAILURE| " dpdklab
2024-05-16  1:10 ` |SUCCESS| " dpdklab
2024-05-16  1:11 ` |FAILURE| " dpdklab
2024-05-16  1:11 ` |SUCCESS| " dpdklab
2024-05-16  1:12 ` |FAILURE| " dpdklab
2024-05-16  1:12 ` |SUCCESS| " dpdklab
2024-05-16  1:16 ` dpdklab
2024-05-16  1:26 ` dpdklab
2024-05-16  1:26 ` |FAILURE| " dpdklab
2024-05-16  1:33 ` |SUCCESS| " dpdklab
2024-05-16  1:42 ` dpdklab
2024-05-16  1:43 ` dpdklab
2024-05-16  1:45 ` dpdklab
2024-05-16  1:45 ` dpdklab
2024-05-16  1:48 ` dpdklab
2024-05-16  1:49 ` dpdklab
2024-05-16  1:51 ` dpdklab
2024-05-16  1:54 ` dpdklab
2024-05-16  1:56 ` dpdklab
2024-05-16  1:56 ` dpdklab
2024-05-16  1:57 ` dpdklab
2024-05-16  2:03 ` dpdklab
2024-05-16  2:03 ` dpdklab
2024-05-16  2:07 ` 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=20240515234413.2799E121E57@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).