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| pw152495 [PATCH] crypto/qat: fix out-of-place header bytes in aead raw api
Date: Thu, 20 Mar 2025 14:03:39 -0400	[thread overview]
Message-ID: <20250320180339.1728927-1-robot@bytheb.org> (raw)
In-Reply-To: <20250320165702.1439228-1-arkadiuszx.kusztal@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2025-03-20 18:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250320165702.1439228-1-arkadiuszx.kusztal@intel.com>
2025-03-20 16:47 ` qemudev
2025-03-20 16:51 ` qemudev
2025-03-20 16:57 ` checkpatch
2025-03-20 18:03 ` 0-day Robot [this message]
2025-03-20 19:22 ` |SUCCESS| pw152495 [PATCH] crypto/qat: fix out-of-place header bytes dpdklab
2025-03-20 19:23 ` |PENDING| " dpdklab
2025-03-20 19:38 ` |SUCCESS| " dpdklab
2025-03-20 19:41 ` dpdklab
2025-03-20 19:49 ` dpdklab
2025-03-20 19:51 ` |PENDING| " dpdklab
2025-03-20 19:51 ` |SUCCESS| " dpdklab
2025-03-20 19:58 ` dpdklab
2025-03-20 19:58 ` dpdklab
2025-03-20 20:01 ` |PENDING| " dpdklab
2025-03-20 20:02 ` |SUCCESS| " dpdklab
2025-03-20 20:08 ` dpdklab
2025-03-20 20:10 ` dpdklab
2025-03-20 20:12 ` dpdklab
2025-03-20 20:12 ` dpdklab
2025-03-20 20:36 ` dpdklab
2025-03-20 20:38 ` dpdklab
2025-03-20 20:38 ` dpdklab
2025-03-20 20:38 ` dpdklab
2025-03-20 20:40 ` |PENDING| " dpdklab
2025-03-20 20:40 ` |SUCCESS| " dpdklab
2025-03-20 20:40 ` dpdklab
2025-03-20 20:41 ` dpdklab
2025-03-20 21:11 ` dpdklab
2025-03-20 21:22 ` dpdklab
2025-03-20 21:57 ` dpdklab
2025-03-21 21: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=20250320180339.1728927-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).