From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw156509 [PATCH v2 3/3] net/mlx5: fix ESP header match after UDP for group 0
Date: Tue, 9 Sep 2025 03:59:24 -0400 [thread overview]
Message-ID: <20250909075924.1625992-1-robot@bytheb.org> (raw)
In-Reply-To: <20250909062853.60592-3-mkashani@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/156509/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/17
next prev parent reply other threads:[~2025-09-09 7:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250909062853.60592-3-mkashani@nvidia.com>
2025-09-09 5:55 ` |SUCCESS| pw156507-156509 " qemudev
2025-09-09 6:00 ` qemudev
2025-09-09 6:27 ` |SUCCESS| pw156509 " checkpatch
2025-09-09 6:59 ` |SUCCESS| pw156507-156509 [PATCH] [v2,3/3] net/mlx5: fix ESP header dpdklab
2025-09-09 7:01 ` dpdklab
2025-09-09 7:03 ` |PENDING| " dpdklab
2025-09-09 7:06 ` |SUCCESS| " dpdklab
2025-09-09 7:06 ` dpdklab
2025-09-09 7:27 ` dpdklab
2025-09-09 7:33 ` dpdklab
2025-09-09 7:34 ` |PENDING| " dpdklab
2025-09-09 7:36 ` dpdklab
2025-09-09 7:36 ` |FAILURE| " dpdklab
2025-09-09 7:56 ` |SUCCESS| " dpdklab
2025-09-09 7:59 ` |SUCCESS| pw156509 [PATCH v2 3/3] net/mlx5: fix ESP header match after UDP for group 0 0-day Robot
2025-09-09 7:59 ` 0-day Robot [this message]
2025-09-09 8:01 ` |SUCCESS| pw156507-156509 [PATCH] [v2,3/3] net/mlx5: fix ESP header dpdklab
2025-09-09 8:11 ` |FAILURE| " dpdklab
2025-09-09 8:19 ` |WARNING| " dpdklab
2025-09-09 8:21 ` |SUCCESS| " dpdklab
2025-09-09 8:40 ` dpdklab
2025-09-09 8:42 ` |FAILURE| " dpdklab
2025-09-09 8:50 ` dpdklab
2025-09-09 8:56 ` |SUCCESS| " dpdklab
2025-09-09 10:55 ` |FAILURE| " dpdklab
2025-09-09 12:07 ` dpdklab
2025-09-09 12:42 ` |WARNING| " 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=20250909075924.1625992-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).