automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw97570 [PATCH v2] eventdev: update crypto adapter metadata structures
Date: Mon, 30 Aug 2021 22:00:19 +0200 (CEST)	[thread overview]
Message-ID: <20210830200019.570AD1226B3@dpdk.org> (raw)
In-Reply-To: <a58110ca3d35bc1bbd78f0f1887d467a4be11b40.1630353395.git.sthotton@marvell.com>

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

_coding style OK_



       reply	other threads:[~2021-08-30 20:00 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a58110ca3d35bc1bbd78f0f1887d467a4be11b40.1630353395.git.sthotton@marvell.com>
2021-08-30 20:00 ` checkpatch [this message]
2021-08-30 22:05 ` [dpdk-test-report] |SUCCESS| pw97570 [dpdk-dev] " 0-day Robot
2021-08-31  0:33 [dpdk-test-report] |SUCCESS| pw97570 [PATCH] [v2] " dpdklab
2021-08-31  0:54 dpdklab
2021-08-31  0:56 dpdklab
2021-08-31  0:59 dpdklab
2021-08-31  0:59 dpdklab
2021-08-31  1:07 dpdklab
2021-08-31  1:20 dpdklab
2021-08-31  1:24 dpdklab
2021-08-31  1:27 dpdklab
2021-08-31  1:43 dpdklab
2021-08-31  1:51 dpdklab
2021-08-31  2:00 dpdklab
2021-08-31  2:06 dpdklab
2021-08-31  2:10 dpdklab
2021-08-31  2:13 dpdklab
2021-08-31  2:13 dpdklab
2021-08-31  2:16 dpdklab
2021-08-31  2:28 dpdklab
2021-08-31  2:31 dpdklab
2021-08-31  2:32 dpdklab
2021-08-31  2:35 dpdklab
2021-08-31  2:41 dpdklab
2021-08-31  2:59 dpdklab
2021-08-31  3:00 dpdklab
2021-08-31  3:00 dpdklab
2021-08-31  3:09 dpdklab
2021-08-31  3:11 dpdklab
2021-08-31  3:13 dpdklab
2021-08-31  3:20 dpdklab
2021-08-31  3:25 dpdklab
2021-08-31  3:29 dpdklab
2021-08-31  3:41 dpdklab
2021-08-31  3:41 dpdklab
2021-08-31  3:43 dpdklab
2021-08-31  3:58 dpdklab
2021-08-31  4:00 dpdklab
2021-08-31  4:06 dpdklab
2021-08-31  4:17 dpdklab
2021-08-31  4:19 dpdklab
2021-08-31  4:29 dpdklab
2021-08-31  4:38 dpdklab
2021-08-31  5:00 dpdklab
2021-08-31  5:06 dpdklab
2021-08-31  5:20 dpdklab
2021-08-31  5:27 dpdklab
2021-08-31  5:31 dpdklab
2021-08-31  5:31 dpdklab
2021-08-31  6:10 dpdklab
2021-08-31  6:16 dpdklab
2021-08-31 17:27 dpdklab
2021-08-31 17:46 dpdklab
2021-08-31 18:05 dpdklab
2021-08-31 18:24 dpdklab
2021-08-31 18:44 dpdklab
2021-08-31 19:05 dpdklab
2021-08-31 19:37 dpdklab
2021-08-31 19:45 dpdklab
2021-08-31 20:00 dpdklab
2021-08-31 20:22 dpdklab
2021-08-31 20:40 dpdklab
2021-08-31 20:56 dpdklab
2021-08-31 21:19 dpdklab
2021-08-31 21:44 dpdklab
2021-08-31 22:01 dpdklab
2021-08-31 22:18 dpdklab
2021-08-31 22:38 dpdklab
2021-08-31 22:59 dpdklab
2021-09-01  0:52 dpdklab
2021-09-01  2:21 dpdklab
2021-09-01  4:26 dpdklab
2021-09-01  6:26 dpdklab
2021-09-01 10:22 dpdklab
2021-09-01 16:23 dpdklab
2021-09-01 17:19 dpdklab
2021-09-01 19:35 dpdklab
2021-09-01 20:55 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=20210830200019.570AD1226B3@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).