automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138140 [PATCH v4 3/3] testpmd: replace EAL logtype TESTPMD_LOG
Date: Fri,  8 Mar 2024 23:36:23 +0100 (CET)	[thread overview]
Message-ID: <20240308223623.7C1FD1223EF@dpdk.org> (raw)
In-Reply-To: <20240308223446.215726-4-stephen@networkplumber.org>

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

_coding style OK_



  parent reply	other threads:[~2024-03-08 22:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308223446.215726-4-stephen@networkplumber.org>
2024-03-08 22:13 ` |SUCCESS| pw138138-138140 " qemudev
2024-03-08 22:17 ` qemudev
2024-03-08 22:36 ` checkpatch [this message]
2024-03-08 23:22 ` |SUCCESS| pw138140 " 0-day Robot
2024-03-09  0:25 ` |SUCCESS| pw138138-138140 [PATCH] [v4,3/3] testpmd: replace EAL logt dpdklab
2024-03-09  0:26 ` dpdklab
2024-03-09  0:26 ` dpdklab
2024-03-09  0:26 ` dpdklab
2024-03-09  0:26 ` dpdklab
2024-03-09  0:27 ` dpdklab
2024-03-09  0:27 ` dpdklab
2024-03-09  0:27 ` dpdklab
2024-03-09  0:27 ` dpdklab
2024-03-09  0:27 ` dpdklab
2024-03-09  0:30 ` dpdklab
2024-03-09  0:45 ` dpdklab
2024-03-09  0:46 ` dpdklab
2024-03-09  0:46 ` dpdklab
2024-03-09  0:47 ` dpdklab
2024-03-09  0:47 ` dpdklab
2024-03-09  0:47 ` dpdklab
2024-03-09  0:48 ` dpdklab
2024-03-09  0:48 ` dpdklab
2024-03-09  0:48 ` dpdklab
2024-03-09  0:49 ` dpdklab
2024-03-09  0:49 ` dpdklab
2024-03-09  0:49 ` dpdklab
2024-03-09  0:49 ` dpdklab
2024-03-09  0:50 ` dpdklab
2024-03-09  0:50 ` dpdklab
2024-03-09  0:50 ` dpdklab
2024-03-09  0:50 ` dpdklab
2024-03-09  0:51 ` dpdklab
2024-03-09  0:52 ` dpdklab
2024-03-09  0:52 ` dpdklab
2024-03-09  0:52 ` dpdklab
2024-03-09  0:52 ` dpdklab
2024-03-09  0:53 ` dpdklab
2024-03-09  0:53 ` dpdklab
2024-03-09  0:53 ` dpdklab
2024-03-09  0:53 ` dpdklab
2024-03-09  0:54 ` dpdklab
2024-03-09  0:54 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  0:55 ` dpdklab
2024-03-09  0:57 ` dpdklab
2024-03-09  1:09 ` dpdklab
2024-03-09  1:09 ` dpdklab
2024-03-09  1:10 ` dpdklab
2024-03-09  1:10 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:11 ` dpdklab
2024-03-09  1:12 ` dpdklab
2024-03-09  1:12 ` dpdklab
2024-03-09  1:12 ` dpdklab
2024-03-09  1:13 ` dpdklab
2024-03-09  1:13 ` dpdklab
2024-03-09  1:14 ` dpdklab
2024-03-09  1:14 ` dpdklab
2024-03-09  1:14 ` dpdklab
2024-03-09  1:15 ` dpdklab
2024-03-09  1:15 ` dpdklab
2024-03-09  1:18 ` dpdklab
2024-03-09  1:39 ` |FAILURE| " dpdklab
2024-03-09  1:42 ` |SUCCESS| " dpdklab
2024-03-09  2:33 ` dpdklab
2024-03-09  3:27 ` dpdklab
2024-03-13 18:14 ` dpdklab
2024-03-13 18:51 ` 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=20240308223623.7C1FD1223EF@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).