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| pw136131 [PATCH] vdpa/mlx5: fix queue enable drain CQ
Date: Wed, 24 Jan 2024 23:24:04 -0500	[thread overview]
Message-ID: <20240125042404.1866976-1-robot@bytheb.org> (raw)
In-Reply-To: <20240125031755.657102-1-yajunw@nvidia.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-01-25  4:24 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240125031755.657102-1-yajunw@nvidia.com>
2024-01-25  2:55 ` qemudev
2024-01-25  3:00 ` qemudev
2024-01-25  3:20 ` checkpatch
2024-01-25  4:24 ` 0-day Robot [this message]
2024-01-25 13:55 dpdklab
2024-01-25 14:06 dpdklab
2024-01-25 14:06 dpdklab
2024-01-25 14:08 dpdklab
2024-01-25 14:09 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:10 dpdklab
2024-01-25 14:11 dpdklab
2024-01-25 14:11 dpdklab
2024-01-25 14:12 dpdklab
2024-01-25 14:12 dpdklab
2024-01-25 14:16 dpdklab
2024-01-25 14:17 dpdklab
2024-01-25 14:17 dpdklab
2024-01-25 14:19 dpdklab
2024-01-25 14:26 dpdklab
2024-01-25 14:35 dpdklab
2024-01-25 14:41 dpdklab
2024-01-25 15:19 dpdklab
2024-01-25 15:28 dpdklab
2024-01-25 15:28 dpdklab
2024-01-25 15:29 dpdklab
2024-01-25 15:39 dpdklab
2024-01-25 15:39 dpdklab
2024-01-25 15:42 dpdklab
2024-01-25 15:42 dpdklab
2024-01-25 15:44 dpdklab
2024-01-25 15:45 dpdklab
2024-01-25 15:48 dpdklab
2024-01-25 15:49 dpdklab
2024-01-25 15:51 dpdklab
2024-01-25 15:52 dpdklab
2024-01-25 15:55 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:56 dpdklab
2024-01-25 15:58 dpdklab
2024-01-25 15:59 dpdklab
2024-01-25 16:00 dpdklab
2024-01-25 16:14 dpdklab
2024-01-25 16:14 dpdklab
2024-01-25 16:15 dpdklab
2024-01-25 16:27 dpdklab
2024-01-25 16:28 dpdklab
2024-01-25 16:32 dpdklab
2024-01-25 16:38 dpdklab
2024-01-25 16:43 dpdklab
2024-01-25 16:50 dpdklab
2024-01-25 16:51 dpdklab
2024-01-25 16:56 dpdklab
2024-01-25 16:59 dpdklab
2024-01-25 17:05 dpdklab
2024-01-25 17:07 dpdklab
2024-01-25 17:08 dpdklab
2024-01-25 17:20 dpdklab
2024-01-25 17:22 dpdklab
2024-01-25 17:26 dpdklab
2024-01-25 17:28 dpdklab
2024-01-25 17:46 dpdklab
2024-01-25 17:51 dpdklab
2024-01-25 18:09 dpdklab
2024-01-26 18:26 dpdklab
2024-01-26 18:40 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=20240125042404.1866976-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).