automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw123360 [PATCH v5] app/procinfo: display eventdev xstats for PMD data
Date: Tue,  7 Feb 2023 17:34:47 +0100 (CET)	[thread overview]
Message-ID: <20230207163448.01E13121E50@dpdk.org> (raw)
In-Reply-To: <20230207163309.3070261-1-abdullah.sevincer@intel.com>

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

_coding style OK_



  parent reply	other threads:[~2023-02-07 16:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230207163309.3070261-1-abdullah.sevincer@intel.com>
2023-02-07 16:27 ` qemudev
2023-02-07 16:31 ` qemudev
2023-02-07 16:34 ` checkpatch [this message]
2023-02-07 19:00 ` 0-day Robot
2023-02-07 17:01 |SUCCESS| pw123360 [PATCH] [v5] " dpdklab
2023-02-07 17:08 dpdklab
2023-02-07 17:11 dpdklab
2023-02-07 17:13 dpdklab
2023-02-07 17:16 dpdklab
2023-02-07 17:24 dpdklab
2023-02-07 17:25 dpdklab
2023-02-07 17:33 dpdklab
2023-02-07 17:50 dpdklab
2023-02-07 18:05 dpdklab
2023-02-07 18:12 dpdklab
2023-02-07 19:57 dpdklab
2023-02-08 14:56 dpdklab
2023-02-08 15:19 dpdklab
2023-02-08 15:31 dpdklab
2023-02-08 15:31 dpdklab
2023-02-08 15:31 dpdklab
2023-02-08 15:37 dpdklab
2023-02-08 15:52 dpdklab
2023-02-08 15:52 dpdklab
2023-02-08 15:58 dpdklab
2023-02-08 15:58 dpdklab
2023-02-09  3:26 dpdklab
2023-02-09  6:40 dpdklab
2023-02-12 19:35 dpdklab
2023-02-12 20:01 dpdklab
2023-02-12 20:02 dpdklab
2023-02-12 20:03 dpdklab
2023-02-12 20:04 dpdklab
2023-02-12 20:05 dpdklab
2023-02-12 20:05 dpdklab
2023-02-12 20:06 dpdklab
2023-02-12 20:16 dpdklab
2023-02-12 20:29 dpdklab
2023-02-12 20:39 dpdklab
2023-02-12 20:43 dpdklab
2023-02-12 20:43 dpdklab
2023-02-12 20:44 dpdklab
2023-02-12 21:47 dpdklab
2023-02-16 17:52 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=20230207163448.01E13121E50@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).