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| pw143339 [RFC] ethdev: jump to table support
Date: Thu, 22 Aug 2024 17:23:02 -0400	[thread overview]
Message-ID: <20240822212302.2976858-1-robot@bytheb.org> (raw)
In-Reply-To: <20240822202753.3856703-1-akozyrev@nvidia.com>

From: robot@bytheb.org

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

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

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

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240822202753.3856703-1-akozyrev@nvidia.com>
2024-08-22 20:02 ` qemudev
2024-08-22 20:06 ` qemudev
2024-08-22 20:28 ` checkpatch
2024-08-22 21:23 ` 0-day Robot [this message]
2024-08-23 12:13 ` |SUCCESS| pw143339 [PATCH] " dpdklab
2024-08-23 12:18 ` dpdklab
2024-08-23 12:25 ` dpdklab
2024-08-23 12:33 ` dpdklab
2024-08-23 12:43 ` dpdklab
2024-08-23 12:49 ` dpdklab
2024-08-23 12:52 ` dpdklab
2024-08-23 13:04 ` dpdklab
2024-08-23 13:06 ` dpdklab
2024-08-23 13:38 ` dpdklab
2024-08-23 14:05 ` dpdklab
2024-08-23 19:24 ` |PENDING| " dpdklab
2024-08-23 19:35 ` |SUCCESS| " dpdklab
2024-08-23 19:36 ` dpdklab
2024-08-23 19:36 ` dpdklab
2024-08-23 19:36 ` dpdklab
2024-08-23 19:37 ` dpdklab
2024-08-23 19:37 ` dpdklab
2024-08-23 19:38 ` dpdklab
2024-08-23 19:38 ` dpdklab
2024-08-23 19:39 ` dpdklab
2024-08-23 20:31 ` dpdklab
2024-08-23 22:03 ` dpdklab
2024-08-23 22:15 ` dpdklab
2024-08-23 22:26 ` dpdklab
2024-08-23 22:26 ` dpdklab
2024-08-23 22:26 ` dpdklab
2024-08-23 22:40 ` dpdklab
2024-08-24  0:04 ` dpdklab
2024-09-20 20:50 ` dpdklab
2024-09-20 21:09 ` 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=20240822212302.2976858-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).