From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137479 [PATCH v2 11/11] net/mlx5: remove unneeded device status checking
Date: Thu, 29 Feb 2024 12:54:42 +0100 (CET) [thread overview]
Message-ID: <20240229115442.9293A12232A@dpdk.org> (raw)
In-Reply-To: <20240229115157.201671-12-dsosnowski@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137479
_coding style OK_
next prev parent reply other threads:[~2024-02-29 11:54 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229115157.201671-12-dsosnowski@nvidia.com>
2024-02-29 11:32 ` |SUCCESS| pw137469-137479 " qemudev
2024-02-29 11:36 ` qemudev
2024-02-29 11:54 ` checkpatch [this message]
2024-02-29 14:01 ` |SUCCESS| pw137469-137479 [PATCH] [v2,11/11] net/mlx5: remove unneed dpdklab
2024-02-29 14:10 ` dpdklab
2024-02-29 14:12 ` dpdklab
2024-02-29 14:13 ` dpdklab
2024-02-29 14:19 ` dpdklab
2024-02-29 14:19 ` dpdklab
2024-02-29 14:34 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:46 ` dpdklab
2024-02-29 14:53 ` dpdklab
2024-02-29 14:54 ` dpdklab
2024-02-29 14:54 ` dpdklab
2024-02-29 14:55 ` dpdklab
2024-02-29 14:59 ` dpdklab
2024-02-29 14:59 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:26 ` dpdklab
2024-02-29 16:04 ` dpdklab
2024-02-29 16:05 ` dpdklab
2024-02-29 16:05 ` dpdklab
2024-02-29 16:05 ` dpdklab
2024-02-29 16:07 ` dpdklab
2024-02-29 16:07 ` dpdklab
2024-02-29 16:07 ` dpdklab
2024-02-29 16:08 ` dpdklab
2024-02-29 16:08 ` dpdklab
2024-02-29 16:10 ` dpdklab
2024-02-29 16:10 ` dpdklab
2024-02-29 16:11 ` dpdklab
2024-02-29 16:11 ` dpdklab
2024-02-29 16:12 ` dpdklab
2024-02-29 16:13 ` dpdklab
2024-02-29 16:13 ` dpdklab
2024-02-29 16:13 ` dpdklab
2024-02-29 16:14 ` dpdklab
2024-02-29 16:14 ` dpdklab
2024-02-29 16:15 ` dpdklab
2024-02-29 16:15 ` dpdklab
2024-02-29 16:15 ` dpdklab
2024-02-29 16:16 ` dpdklab
2024-02-29 16:16 ` dpdklab
2024-02-29 16:16 ` dpdklab
2024-02-29 16:17 ` dpdklab
2024-02-29 16:17 ` dpdklab
2024-02-29 16:18 ` dpdklab
2024-02-29 16:19 ` dpdklab
2024-02-29 16:19 ` dpdklab
2024-02-29 16:20 ` dpdklab
2024-02-29 16:20 ` dpdklab
2024-02-29 16:21 ` dpdklab
2024-02-29 16:21 ` dpdklab
2024-02-29 16:21 ` dpdklab
2024-02-29 16:22 ` dpdklab
2024-02-29 16:22 ` dpdklab
2024-02-29 16:22 ` dpdklab
2024-02-29 16:23 ` dpdklab
2024-02-29 16:23 ` dpdklab
2024-02-29 16:24 ` dpdklab
2024-02-29 16:27 ` dpdklab
2024-02-29 16:44 ` dpdklab
2024-02-29 16:47 ` dpdklab
2024-02-29 17:33 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-03-01 6:43 ` dpdklab
2024-03-01 6:45 ` dpdklab
2024-03-01 6:49 ` dpdklab
2024-03-01 6:53 ` dpdklab
2024-03-02 6:17 ` dpdklab
2024-03-03 1:27 ` dpdklab
2024-03-03 2:00 ` dpdklab
2024-03-03 2:32 ` 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=20240229115442.9293A12232A@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).