automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140393 [PATCH v2 2/2] crypto: validate crypto callbacks from next node
Date: Wed, 29 May 2024 16:41:56 +0200 (CEST)	[thread overview]
Message-ID: <20240529144156.2695712367B@dpdk.org> (raw)
In-Reply-To: <20240529144025.4089318-2-ganapati.kundapura@intel.com>

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

_coding style OK_



  parent reply	other threads:[~2024-05-29 14:41 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240529144025.4089318-2-ganapati.kundapura@intel.com>
2024-05-29 14:19 ` |SUCCESS| pw140392-140393 " qemudev
2024-05-29 14:24 ` qemudev
2024-05-29 14:41 ` checkpatch [this message]
2024-05-29 15:51 ` |SUCCESS| pw140392-140393 [PATCH] [v2,2/2] crypto: validate crypto c dpdklab
2024-05-29 15:57 ` dpdklab
2024-05-29 16:01 ` dpdklab
2024-05-29 16:02 ` dpdklab
2024-05-29 16:03 ` dpdklab
2024-05-29 16:04 ` dpdklab
2024-05-29 16:12 ` dpdklab
2024-05-29 16:12 ` dpdklab
2024-05-29 16:13 ` dpdklab
2024-05-29 16:13 ` dpdklab
2024-05-29 16:13 ` dpdklab
2024-05-29 16:13 ` dpdklab
2024-05-29 16:14 ` dpdklab
2024-05-29 16:14 ` dpdklab
2024-05-29 16:14 ` dpdklab
2024-05-29 16:14 ` dpdklab
2024-05-29 16:15 ` dpdklab
2024-05-29 16:15 ` dpdklab
2024-05-29 16:15 ` dpdklab
2024-05-29 16:16 ` dpdklab
2024-05-29 16:16 ` dpdklab
2024-05-29 16:16 ` dpdklab
2024-05-29 16:17 ` dpdklab
2024-05-29 16:18 ` dpdklab
2024-05-29 16:18 ` dpdklab
2024-05-29 16:19 ` dpdklab
2024-05-29 16:20 ` dpdklab
2024-05-29 16:21 ` dpdklab
2024-05-29 16:21 ` dpdklab
2024-05-29 16:21 ` dpdklab
2024-05-29 16:22 ` dpdklab
2024-05-29 16:22 ` dpdklab
2024-05-29 16:22 ` dpdklab
2024-05-29 16:22 ` dpdklab
2024-05-29 16:23 ` dpdklab
2024-05-29 16:23 ` dpdklab
2024-05-29 16:23 ` dpdklab
2024-05-29 16:23 ` dpdklab
2024-05-29 16:24 ` dpdklab
2024-05-29 16:24 ` dpdklab
2024-05-29 16:25 ` dpdklab
2024-05-29 16:25 ` dpdklab
2024-05-29 16:26 ` dpdklab
2024-05-29 16:26 ` dpdklab
2024-05-29 16:26 ` dpdklab
2024-05-29 16:27 ` dpdklab
2024-05-29 16:27 ` dpdklab
2024-05-29 16:27 ` dpdklab
2024-05-29 16:28 ` dpdklab
2024-05-29 16:33 ` dpdklab
2024-05-29 16:33 ` dpdklab
2024-05-29 16:35 ` dpdklab
2024-05-29 16:36 ` dpdklab
2024-05-29 16:37 ` dpdklab
2024-05-29 16:37 ` dpdklab
2024-05-29 16:38 ` dpdklab
2024-05-29 16:39 ` dpdklab
2024-05-29 16:39 ` dpdklab
2024-05-29 16:40 ` dpdklab
2024-05-29 16:40 ` dpdklab
2024-05-29 16:41 ` dpdklab
2024-05-29 16:41 ` dpdklab
2024-05-29 16:42 ` dpdklab
2024-05-29 16:43 ` dpdklab
2024-05-29 16:44 ` dpdklab
2024-05-29 16:45 ` dpdklab
2024-05-29 16:46 ` dpdklab
2024-05-29 16:46 ` dpdklab
2024-05-29 16:46 ` dpdklab
2024-05-29 16:46 ` dpdklab
2024-05-29 16:46 ` dpdklab
2024-05-29 16:47 ` dpdklab
2024-05-29 16:49 ` dpdklab
2024-05-29 16:50 ` |SUCCESS| pw140393 [PATCH v2 2/2] crypto: validate crypto callbacks from next node 0-day Robot
2024-05-29 16:50 ` |SUCCESS| pw140392-140393 [PATCH] [v2,2/2] crypto: validate crypto c dpdklab
2024-05-29 16:50 ` dpdklab
2024-05-29 16:51 ` dpdklab
2024-05-29 16:51 ` dpdklab
2024-05-29 16:52 ` dpdklab
2024-05-29 16:54 ` dpdklab
2024-05-29 16:55 ` dpdklab
2024-05-29 16:55 ` dpdklab
2024-05-29 17:22 ` dpdklab
2024-05-29 17:22 ` dpdklab
2024-05-29 17:23 ` dpdklab
2024-05-30  6:17 ` dpdklab
2024-05-30  6:17 ` dpdklab
2024-05-30  6: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=20240529144156.2695712367B@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).