automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141995 [PATCH] dpdk-pmdinfo: remove unneeded whitespace
Date: Mon,  1 Jul 2024 19:59:35 +0200 (CEST)	[thread overview]
Message-ID: <20240701175935.82ACA128144@dpdk.org> (raw)
In-Reply-To: <20240701175840.18368-1-stephen@networkplumber.org>

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

_coding style OK_



  parent reply	other threads:[~2024-07-01 17:59 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240701175840.18368-1-stephen@networkplumber.org>
2024-07-01 17:32 ` qemudev
2024-07-01 17:37 ` qemudev
2024-07-01 17:59 ` checkpatch [this message]
2024-07-01 18:45 ` 0-day Robot
2024-07-02  0:26 ` dpdklab
2024-07-02  0:30 ` dpdklab
2024-07-02  0:34 ` |PENDING| " dpdklab
2024-07-02  0:36 ` dpdklab
2024-07-02  0:40 ` |SUCCESS| " dpdklab
2024-07-02  0:40 ` dpdklab
2024-07-02  0:41 ` dpdklab
2024-07-02  0:50 ` |PENDING| " dpdklab
2024-07-02  0:52 ` |SUCCESS| " dpdklab
2024-07-02  0:53 ` dpdklab
2024-07-02  1:02 ` dpdklab
2024-07-02  1:09 ` |PENDING| " dpdklab
2024-07-02  1:11 ` |FAILURE| " dpdklab
2024-07-02  2:14 ` |PENDING| " dpdklab
2024-07-02  2:21 ` dpdklab
2024-07-02  2:33 ` dpdklab
2024-07-02  2:33 ` dpdklab
2024-07-02  2:38 ` dpdklab
2024-07-02  2:38 ` dpdklab
2024-07-02  2:41 ` dpdklab
2024-07-02  2:43 ` dpdklab
2024-07-02  2:45 ` |FAILURE| " dpdklab
2024-07-02  2:47 ` |PENDING| " dpdklab
2024-07-02  2:51 ` |FAILURE| " dpdklab
2024-07-02  2:53 ` |PENDING| " dpdklab
2024-07-02  2:56 ` |FAILURE| " dpdklab
2024-07-02  2:58 ` |PENDING| " dpdklab
2024-07-02  2:59 ` dpdklab
2024-07-02  3:00 ` dpdklab
2024-07-02  3:00 ` |FAILURE| " dpdklab
2024-07-02  3:01 ` |PENDING| " dpdklab
2024-07-02  3:01 ` |FAILURE| " dpdklab
2024-07-02  3:03 ` |PENDING| " dpdklab
2024-07-02  3:04 ` |FAILURE| " dpdklab
2024-07-02  3:05 ` |PENDING| " dpdklab
2024-07-02  3:11 ` |FAILURE| " dpdklab
2024-07-02  3:11 ` |SUCCESS| " dpdklab
2024-07-02  3:17 ` |FAILURE| " dpdklab
2024-07-02  3:20 ` dpdklab
2024-07-02  3:20 ` dpdklab
2024-07-02  3:22 ` dpdklab
2024-07-02  3:23 ` dpdklab
2024-07-02  3:29 ` dpdklab
2024-07-02  3:30 ` dpdklab
2024-07-02  3:31 ` dpdklab
2024-07-02  3:34 ` dpdklab
2024-07-02  5:05 ` |PENDING| " dpdklab
2024-07-02  5:05 ` dpdklab
2024-07-02  5:06 ` dpdklab
2024-07-02  5:08 ` dpdklab
2024-07-02  5:09 ` dpdklab
2024-07-02  5:14 ` dpdklab
2024-07-02  5:17 ` dpdklab
2024-07-02  5:17 ` dpdklab
2024-07-02  5:18 ` dpdklab
2024-07-02  5:20 ` dpdklab
2024-07-02  5:22 ` dpdklab
2024-07-02  5:23 ` dpdklab
2024-07-02  5:23 ` dpdklab
2024-07-02  5:25 ` dpdklab
2024-07-02  5:28 ` dpdklab
2024-07-02  5:30 ` dpdklab
2024-07-02  5:31 ` dpdklab
2024-07-02  5:31 ` dpdklab
2024-07-02  5:32 ` dpdklab
2024-07-02  5:36 ` dpdklab
2024-07-02  5:37 ` dpdklab
2024-07-02  5:38 ` dpdklab
2024-07-02  5:38 ` dpdklab
2024-07-02  5:39 ` dpdklab
2024-07-02  5:40 ` dpdklab
2024-07-02  5:43 ` dpdklab
2024-07-02  5:43 ` |SUCCESS| " dpdklab
2024-07-02  5:44 ` dpdklab
2024-07-02  5:49 ` |PENDING| " dpdklab
2024-07-02  5:55 ` dpdklab
2024-07-02  6:05 ` dpdklab
2024-07-02  6:06 ` dpdklab
2024-07-02  6:12 ` dpdklab
2024-07-02  6:14 ` dpdklab
2024-07-02  6:53 ` dpdklab
2024-07-02  7:10 ` dpdklab
2024-07-02  8:00 ` dpdklab
2024-07-02  8:01 ` dpdklab
2024-07-02  8:09 ` dpdklab
2024-07-02  8:10 ` dpdklab
2024-07-02  8:19 ` dpdklab
2024-07-02  8:20 ` dpdklab
2024-07-02  8:25 ` dpdklab
2024-07-02  8:32 ` dpdklab
2024-07-02  8:49 ` dpdklab
2024-07-02  8:59 ` dpdklab
2024-07-02  9:02 ` dpdklab
2024-07-02  9:10 ` dpdklab
2024-07-02  9:18 ` dpdklab
2024-07-02  9:23 ` dpdklab
2024-07-02  9:27 ` dpdklab
2024-07-02  9:30 ` |SUCCESS| " dpdklab
2024-07-02  9:40 ` dpdklab
2024-07-02 12:55 ` dpdklab
2024-07-02 16:12 ` dpdklab
2024-07-02 16:24 ` 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=20240701175935.82ACA128144@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).