automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143651 [PATCH] [RFC] cryptodev: replace LIST_END enumerators with APIs
Date: Thu,  5 Sep 2024 07:04:34 -0400	[thread overview]
Message-ID: <20240905110434.3998774-1-robot@bytheb.org> (raw)
In-Reply-To: <20240905101438.3888274-1-gakhil@marvell.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143651/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10718609941

  parent reply	other threads:[~2024-09-05 11:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240905101438.3888274-1-gakhil@marvell.com>
2024-09-05  9:48 ` qemudev
2024-09-05  9:53 ` qemudev
2024-09-05 10:16 ` checkpatch
2024-09-05 11:04 ` 0-day Robot [this message]
2024-09-06  1:49 ` |SUCCESS| pw143651 [PATCH] [RFC] cryptodev: replace LIST_END enumera dpdklab
2024-09-06  6:50 ` |PENDING| " dpdklab
2024-09-06  6:54 ` |SUCCESS| " dpdklab
2024-09-06  8:08 ` |PENDING| " dpdklab
2024-09-06  8:14 ` |SUCCESS| " dpdklab
2024-09-06 11:07 ` dpdklab
2024-09-06 11:08 ` dpdklab
2024-09-06 11:08 ` dpdklab
2024-09-06 11:09 ` dpdklab
2024-09-06 11:11 ` dpdklab
2024-09-06 11:11 ` dpdklab
2024-09-06 11:11 ` dpdklab
2024-09-06 11:12 ` dpdklab
2024-09-06 11:12 ` dpdklab
2024-09-06 11:13 ` dpdklab
2024-09-06 11:14 ` dpdklab
2024-09-06 11:14 ` dpdklab
2024-09-06 11:14 ` dpdklab
2024-09-06 11:16 ` dpdklab
2024-09-06 21:19 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:23 ` dpdklab
2024-09-06 21:24 ` dpdklab
2024-09-06 21:29 ` dpdklab
2024-09-06 21:36 ` dpdklab
2024-09-06 23:49 ` dpdklab
2024-09-07 21:14 ` dpdklab
2024-09-17 14:35 ` dpdklab
2024-09-17 14:50 ` 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=20240905110434.3998774-1-robot@bytheb.org \
    --to=robot@bytheb.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).