From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw155638 [PATCH] net/mlx5/hws: fix ESP header match in strict mode
Date: Mon, 4 Aug 2025 02:24:12 -0400 [thread overview]
Message-ID: <20250804062412.827692-1-robot@bytheb.org> (raw)
In-Reply-To: <20250804050514.244896-1-viacheslavo@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/155638/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/16714790941
next prev parent reply other threads:[~2025-08-04 6:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250804050514.244896-1-viacheslavo@nvidia.com>
2025-08-04 4:35 ` qemudev
2025-08-04 4:40 ` qemudev
2025-08-04 5:04 ` checkpatch
2025-08-04 6:24 ` 0-day Robot [this message]
2025-08-04 6:35 ` |PENDING| pw155638 [PATCH] net/mlx5/hws: fix ESP header match in str dpdklab
2025-08-04 6:37 ` |SUCCESS| " dpdklab
2025-08-04 6:44 ` |FAILURE| " dpdklab
2025-08-04 6:45 ` |SUCCESS| " dpdklab
2025-08-04 6:47 ` |PENDING| " dpdklab
2025-08-04 6:50 ` dpdklab
2025-08-04 6:50 ` |SUCCESS| " dpdklab
2025-08-04 6:55 ` dpdklab
2025-08-04 7:01 ` |FAILURE| " dpdklab
2025-08-04 7:01 ` dpdklab
2025-08-04 7:10 ` |SUCCESS| " dpdklab
2025-08-04 7:12 ` dpdklab
2025-08-04 7:22 ` dpdklab
2025-08-04 7:24 ` dpdklab
2025-08-04 7:29 ` dpdklab
2025-08-04 7:29 ` dpdklab
2025-08-04 7:31 ` dpdklab
2025-08-04 7:49 ` |PENDING| " dpdklab
2025-08-04 7:56 ` |SUCCESS| " dpdklab
2025-08-04 7:56 ` dpdklab
2025-08-04 8:21 ` dpdklab
2025-08-04 8:27 ` dpdklab
2025-08-04 8:46 ` dpdklab
2025-08-04 8:47 ` dpdklab
2025-08-04 8:49 ` dpdklab
2025-08-04 8:50 ` |FAILURE| " dpdklab
2025-08-04 8:57 ` |SUCCESS| " dpdklab
2025-08-04 9:10 ` dpdklab
2025-08-04 9:39 ` 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=20250804062412.827692-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).