automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw143104 [PATCH v7 3/3] event/dsw: add capability for independent enqueue
Date: Mon, 12 Aug 2024 20:44:11 +0200 (CEST)	[thread overview]
Message-ID: <20240812184411.0D613123EF6@dpdk.org> (raw)
In-Reply-To: <20240812184153.982130-4-abdullah.sevincer@intel.com>

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

_coding style OK_



  parent reply	other threads:[~2024-08-12 18:44 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240812184153.982130-4-abdullah.sevincer@intel.com>
2024-08-12 18:15 ` |SUCCESS| pw143102-143104 " qemudev
2024-08-12 18:20 ` qemudev
2024-08-12 18:44 ` checkpatch [this message]
2024-08-12 19:42 ` |FAILURE| pw143104 " 0-day Robot
2024-08-12 20:51 ` |SUCCESS| pw143102-143104 [PATCH] [v7,3/3] event/dsw: add capability dpdklab
2024-08-12 22:08 ` |PENDING| " dpdklab
2024-08-12 22:22 ` |SUCCESS| " dpdklab
2024-08-12 22:38 ` |PENDING| " dpdklab
2024-08-12 22:51 ` |SUCCESS| " dpdklab
2024-08-12 23:09 ` dpdklab
2024-08-12 23:18 ` dpdklab
2024-08-12 23:32 ` dpdklab
2024-08-12 23:41 ` dpdklab
2024-08-13  1:38 ` |PENDING| " dpdklab
2024-08-13  1:46 ` |SUCCESS| " dpdklab
2024-08-13  1:54 ` |PENDING| " dpdklab
2024-08-13  1:58 ` dpdklab
2024-08-13  2:01 ` dpdklab
2024-08-13  2:03 ` |SUCCESS| " dpdklab
2024-08-13  2:04 ` dpdklab
2024-08-13  2:06 ` |PENDING| " dpdklab
2024-08-13  2:11 ` |SUCCESS| " dpdklab
2024-08-13  2:14 ` |PENDING| " dpdklab
2024-08-13  2:21 ` |SUCCESS| " dpdklab
2024-08-13  2:21 ` |PENDING| " dpdklab
2024-08-13  2:23 ` dpdklab
2024-08-13  2:26 ` dpdklab
2024-08-13  2:28 ` dpdklab
2024-08-13  2:29 ` dpdklab
2024-08-13  2:34 ` dpdklab
2024-08-13  2:35 ` dpdklab
2024-08-13  2:37 ` dpdklab
2024-08-13  2:38 ` dpdklab
2024-08-13  2:43 ` dpdklab
2024-08-13  2:45 ` dpdklab
2024-08-13  2:46 ` dpdklab
2024-08-13  2:47 ` dpdklab
2024-08-13  2:48 ` dpdklab
2024-08-13  2:50 ` dpdklab
2024-08-13  2:52 ` dpdklab
2024-08-13  2:52 ` dpdklab
2024-08-13  2:53 ` dpdklab
2024-08-13  2:53 ` dpdklab
2024-08-13  2:53 ` dpdklab
2024-08-13  2:54 ` dpdklab
2024-08-13  2:54 ` dpdklab
2024-08-13  2:54 ` dpdklab
2024-08-13  2:55 ` dpdklab
2024-08-13  2:55 ` dpdklab
2024-08-13  2:56 ` dpdklab
2024-08-13  2:57 ` dpdklab
2024-08-13  2:57 ` dpdklab
2024-08-13  3:00 ` dpdklab
2024-08-13  3:01 ` dpdklab
2024-08-13  3:05 ` dpdklab
2024-08-13  3:08 ` dpdklab
2024-08-13  3:12 ` |SUCCESS| " dpdklab
2024-08-13  3:14 ` |PENDING| " dpdklab
2024-08-13  3:14 ` dpdklab
2024-08-13  3:15 ` dpdklab
2024-08-13  3:19 ` |SUCCESS| " dpdklab
2024-08-13  3:22 ` |PENDING| " dpdklab
2024-08-13  3:30 ` dpdklab
2024-08-13  3:31 ` dpdklab
2024-08-13  3:36 ` dpdklab
2024-08-13  3:37 ` |SUCCESS| " dpdklab
2024-08-13  3:42 ` |PENDING| " dpdklab
2024-08-13  3:42 ` dpdklab
2024-08-13  3:45 ` dpdklab
2024-08-13  3:48 ` dpdklab
2024-08-13  3:54 ` dpdklab
2024-08-13  3:59 ` dpdklab
2024-08-13  4:00 ` dpdklab
2024-08-13  4:01 ` dpdklab
2024-08-13  4:01 ` dpdklab
2024-08-13  4:01 ` dpdklab
2024-08-13  4:01 ` dpdklab
2024-08-13  4:02 ` dpdklab
2024-08-13  4:02 ` dpdklab
2024-08-13  4:07 ` |SUCCESS| " dpdklab
2024-08-13  4:08 ` |PENDING| " dpdklab
2024-08-13  4:09 ` dpdklab
2024-08-13  4:10 ` dpdklab
2024-08-13  4:12 ` |SUCCESS| " dpdklab
2024-08-13  4:16 ` |PENDING| " dpdklab
2024-08-13  4:20 ` dpdklab
2024-08-13  4:21 ` dpdklab
2024-08-13  4:24 ` dpdklab
2024-08-13  4:25 ` dpdklab
2024-08-13  4:27 ` dpdklab
2024-08-13  4:31 ` |SUCCESS| " dpdklab
2024-08-13  4:33 ` |PENDING| " dpdklab
2024-08-13  4:44 ` dpdklab
2024-08-13  4:50 ` dpdklab
2024-08-13  4:55 ` |SUCCESS| " dpdklab
2024-08-13  5:31 ` dpdklab
2024-08-13  5:36 ` |PENDING| " dpdklab
2024-08-13  6:01 ` |SUCCESS| " dpdklab
2024-08-13  9:20 ` 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=20240812184411.0D613123EF6@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).