From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138396 [PATCH 13/13] net/mlx5/hws: fix port ID for root matcher and rule
Date: Thu, 14 Mar 2024 08:43:35 -0400 [thread overview]
Message-ID: <20240314124335.1200800-1-robot@bytheb.org> (raw)
In-Reply-To: <20240314114220.203241-13-igozlan@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138396/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8280349231
next prev parent reply other threads:[~2024-03-14 12:43 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314114220.203241-13-igozlan@nvidia.com>
2024-03-14 11:23 ` |SUCCESS| pw138384-138396 " qemudev
2024-03-14 11:28 ` qemudev
2024-03-14 11:45 ` |SUCCESS| pw138396 " checkpatch
2024-03-14 12:43 ` 0-day Robot [this message]
2024-03-14 17:57 ` |SUCCESS| pw138384-138396 [PATCH] [13/13] net/mlx5/hws: fix port ID dpdklab
2024-03-14 17:59 ` dpdklab
2024-03-14 17:59 ` dpdklab
2024-03-14 18:00 ` dpdklab
2024-03-14 18:01 ` dpdklab
2024-03-14 18:13 ` dpdklab
2024-03-14 18:14 ` dpdklab
2024-03-14 18:14 ` dpdklab
2024-03-14 18:16 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:17 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:18 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:20 ` dpdklab
2024-03-14 18:29 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:32 ` dpdklab
2024-03-14 18:33 ` dpdklab
2024-03-14 18:33 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:34 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:35 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:36 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:38 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:39 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:40 ` dpdklab
2024-03-14 18:41 ` dpdklab
2024-03-14 18:41 ` dpdklab
2024-03-14 18:42 ` dpdklab
2024-03-14 18:43 ` dpdklab
2024-03-14 18:46 ` dpdklab
2024-03-14 18:47 ` dpdklab
2024-03-14 18:47 ` dpdklab
2024-03-14 18:49 ` dpdklab
2024-03-14 18:52 ` dpdklab
2024-03-14 18:57 ` dpdklab
2024-03-14 19:01 ` dpdklab
2024-03-14 19:09 ` dpdklab
2024-03-14 19:13 ` dpdklab
2024-03-14 19:14 ` dpdklab
2024-03-14 19:53 ` dpdklab
2024-03-18 12:44 ` dpdklab
2024-03-18 13:21 ` 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=20240314124335.1200800-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).