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| pw143359 [PATCH v2 18/18] net/dpaa: improve dpaa errata A010022 handling
Date: Fri, 23 Aug 2024 04:23:12 -0400	[thread overview]
Message-ID: <20240823082312.299019-1-robot@bytheb.org> (raw)
In-Reply-To: <20240823073240.3708320-19-hemant.agrawal@nxp.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-08-23  8:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240823073240.3708320-19-hemant.agrawal@nxp.com>
2024-08-23  7:38 ` checkpatch
2024-08-23  7:39 ` |SUCCESS| pw143342-143359 " qemudev
2024-08-23  7:43 ` qemudev
2024-08-23  8:23 ` 0-day Robot [this message]
2024-08-23 19:10 ` |SUCCESS| pw143342-143359 [PATCH] [v2,18/18] net/dpaa: improve dpaa dpdklab
2024-08-23 19:13 ` dpdklab
2024-08-23 19:25 ` dpdklab
2024-08-23 19:28 ` dpdklab
2024-08-23 19:34 ` dpdklab
2024-08-23 20:10 ` dpdklab
2024-08-24  0:53 ` dpdklab
2024-08-24  1:02 ` dpdklab
2024-08-24  1:16 ` dpdklab
2024-08-24  1:26 ` dpdklab
2024-08-24  1:35 ` dpdklab
2024-08-24  1:49 ` dpdklab
2024-08-24  2:23 ` dpdklab
2024-08-24  2:28 ` dpdklab
2024-08-24  2:44 ` dpdklab
2024-08-24  3:35 ` dpdklab
2024-08-24  3:42 ` dpdklab
2024-08-24  3:56 ` dpdklab
2024-08-24  9:29 ` |PENDING| " dpdklab
2024-08-24  9:36 ` dpdklab
2024-08-24 10:06 ` |SUCCESS| " dpdklab
2024-08-24 10:39 ` dpdklab
2024-08-24 10:41 ` dpdklab
2024-08-24 10:41 ` dpdklab
2024-08-24 10:44 ` dpdklab
2024-08-24 14:47 ` dpdklab
2024-08-24 15:17 ` dpdklab
2024-08-24 15:23 ` dpdklab
2024-08-26 15:10 ` dpdklab
2024-08-26 15:11 ` dpdklab
2024-08-26 15:22 ` dpdklab
2024-08-26 15:24 ` 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=20240823082312.299019-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).