From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw153071 [PATCH] net/mlx5: fix out-of-bounds write in Rx software ring
Date: Tue, 22 Apr 2025 08:40:40 +0200 (CEST) [thread overview]
Message-ID: <20250422064040.25A15123FA7@dpdk.org> (raw)
In-Reply-To: <20250422063754.3429965-1-patrykochal@gmail.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/153071
_coding style OK_
next prev parent reply other threads:[~2025-04-22 6:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422063754.3429965-1-patrykochal@gmail.com>
2025-04-22 6:05 ` qemudev
2025-04-22 6:09 ` qemudev
2025-04-22 6:40 ` checkpatch [this message]
2025-04-22 13:25 ` |SUCCESS| pw153071 [PATCH] net/mlx5: fix out-of-bounds write in Rx s dpdklab
2025-04-22 13:35 ` dpdklab
2025-04-22 13:37 ` dpdklab
2025-04-22 13:43 ` dpdklab
2025-04-22 13:48 ` dpdklab
2025-04-22 13:49 ` dpdklab
2025-04-22 13:52 ` dpdklab
2025-04-22 13:59 ` dpdklab
2025-04-22 14:01 ` |FAILURE| " dpdklab
2025-04-22 14:02 ` |PENDING| " dpdklab
2025-04-22 14:04 ` |SUCCESS| " dpdklab
2025-04-22 14:09 ` |FAILURE| " dpdklab
2025-04-22 14:09 ` dpdklab
2025-04-22 14:11 ` dpdklab
2025-04-22 14:13 ` |SUCCESS| " dpdklab
2025-04-22 14:16 ` |FAILURE| " dpdklab
2025-04-22 14:23 ` dpdklab
2025-04-22 14:24 ` dpdklab
2025-04-22 14:24 ` dpdklab
2025-04-22 14:26 ` dpdklab
2025-04-22 14:27 ` dpdklab
2025-04-22 14:31 ` dpdklab
2025-04-22 14:38 ` |WARNING| " dpdklab
2025-04-22 14:39 ` dpdklab
2025-04-22 14:50 ` |SUCCESS| " dpdklab
2025-04-22 14:50 ` dpdklab
2025-04-22 14:51 ` dpdklab
2025-04-22 15:05 ` |FAILURE| " dpdklab
2025-04-22 15:13 ` dpdklab
2025-04-22 15:15 ` dpdklab
2025-04-22 15:16 ` dpdklab
2025-04-22 15:22 ` |WARNING| " dpdklab
2025-04-22 15:25 ` |FAILURE| " dpdklab
2025-04-22 15:26 ` dpdklab
2025-04-22 15:30 ` |WARNING| " dpdklab
2025-04-22 15:47 ` |FAILURE| " dpdklab
2025-04-22 16:05 ` dpdklab
2025-04-22 17:01 ` 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=20250422064040.25A15123FA7@dpdk.org \
--to=checkpatch@dpdk.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).