From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw152193 [PATCH 2/2] net/mlx5: fix non template flow validation on create
Date: Mon, 3 Mar 2025 09:44:17 -0500 [thread overview]
Message-ID: <20250303144417.2071859-1-robot@bytheb.org> (raw)
In-Reply-To: <20250303133450.71626-2-mkashani@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/152193/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13632383170
next prev parent reply other threads:[~2025-03-03 14:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250303133450.71626-2-mkashani@nvidia.com>
2025-03-03 13:04 ` |SUCCESS| pw152192-152193 " qemudev
2025-03-03 13:09 ` qemudev
2025-03-03 13:36 ` |SUCCESS| pw152193 " checkpatch
2025-03-03 14:44 ` 0-day Robot [this message]
2025-03-03 16:17 ` |SUCCESS| pw152192-152193 [PATCH] [2/2] net/mlx5: fix non template f dpdklab
2025-03-03 16:31 ` dpdklab
2025-03-03 16:42 ` dpdklab
2025-03-03 16:51 ` |PENDING| " dpdklab
2025-03-03 16:57 ` |SUCCESS| " dpdklab
2025-03-03 17:01 ` dpdklab
2025-03-03 17:04 ` |PENDING| " dpdklab
2025-03-03 17:07 ` |SUCCESS| " dpdklab
2025-03-03 17:10 ` dpdklab
2025-03-03 17:15 ` dpdklab
2025-03-03 17:19 ` |PENDING| " dpdklab
2025-03-03 17:30 ` |SUCCESS| " dpdklab
2025-03-03 17:34 ` |PENDING| " dpdklab
2025-03-03 17:40 ` |SUCCESS| " dpdklab
2025-03-03 17:45 ` dpdklab
2025-03-03 17:54 ` |PENDING| " dpdklab
2025-03-03 18:51 ` |SUCCESS| " dpdklab
2025-03-03 19:01 ` dpdklab
2025-03-03 19:02 ` dpdklab
2025-03-03 19:21 ` dpdklab
2025-03-03 19:32 ` dpdklab
2025-03-03 19:33 ` 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=20250303144417.2071859-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).