From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137448 [PATCH 11/11] net/mlx5: remove unneeded device status checking
Date: Wed, 28 Feb 2024 18:03:38 +0100 (CET) [thread overview]
Message-ID: <20240228170338.29EE8122320@dpdk.org> (raw)
In-Reply-To: <20240228170046.176600-12-dsosnowski@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137448
_coding style OK_
next prev parent reply other threads:[~2024-02-28 17:03 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228170046.176600-12-dsosnowski@nvidia.com>
2024-02-28 16:41 ` |SUCCESS| pw137441-137448 " qemudev
2024-02-28 16:46 ` qemudev
2024-02-28 17:03 ` checkpatch [this message]
2024-02-28 17:43 ` |SUCCESS| pw137441-137448 [PATCH] [11/11] net/mlx5: remove unneeded dpdklab
2024-02-28 17:44 ` dpdklab
2024-02-28 17:45 ` dpdklab
2024-02-28 17:45 ` dpdklab
2024-02-28 17:46 ` dpdklab
2024-02-28 17:46 ` dpdklab
2024-02-28 17:46 ` dpdklab
2024-02-28 17:48 ` dpdklab
2024-02-28 17:48 ` dpdklab
2024-02-28 17:48 ` dpdklab
2024-02-28 17:49 ` dpdklab
2024-02-28 17:49 ` dpdklab
2024-02-28 17:49 ` dpdklab
2024-02-28 17:49 ` dpdklab
2024-02-28 17:50 ` dpdklab
2024-02-28 17:50 ` dpdklab
2024-02-28 17:50 ` dpdklab
2024-02-28 17:51 ` dpdklab
2024-02-28 17:51 ` dpdklab
2024-02-28 17:52 ` dpdklab
2024-02-28 17:53 ` dpdklab
2024-02-28 17:53 ` dpdklab
2024-02-28 17:54 ` dpdklab
2024-02-28 17:55 ` dpdklab
2024-02-28 17:55 ` dpdklab
2024-02-28 17:56 ` dpdklab
2024-02-28 17:56 ` dpdklab
2024-02-28 17:56 ` dpdklab
2024-02-28 17:57 ` dpdklab
2024-02-28 17:57 ` dpdklab
2024-02-28 17:58 ` dpdklab
2024-02-28 17:58 ` dpdklab
2024-02-28 17:58 ` dpdklab
2024-02-28 17:59 ` dpdklab
2024-02-28 17:59 ` dpdklab
2024-02-28 18:00 ` dpdklab
2024-02-28 18:01 ` dpdklab
2024-02-28 18:01 ` dpdklab
2024-02-28 18:01 ` dpdklab
2024-02-28 18:01 ` dpdklab
2024-02-28 18:03 ` dpdklab
2024-02-28 18:03 ` dpdklab
2024-02-28 18:04 ` dpdklab
2024-02-28 18:05 ` dpdklab
2024-02-28 18:05 ` dpdklab
2024-02-28 18:05 ` dpdklab
2024-02-28 18:06 ` dpdklab
2024-02-28 18:08 ` dpdklab
2024-02-28 18:08 ` dpdklab
2024-02-28 18:11 ` dpdklab
2024-02-28 18:11 ` dpdklab
2024-02-28 18:14 ` dpdklab
2024-02-28 18:15 ` dpdklab
2024-02-28 18:15 ` dpdklab
2024-02-28 18:16 ` dpdklab
2024-02-28 18:17 ` dpdklab
2024-02-28 18:21 ` dpdklab
2024-02-28 18:42 ` dpdklab
2024-02-28 19:05 ` dpdklab
2024-02-28 19:08 ` dpdklab
2024-02-28 22:07 ` dpdklab
2024-02-28 22:14 ` dpdklab
2024-02-29 17:35 ` dpdklab
2024-03-01 0:14 ` dpdklab
2024-03-01 0:23 ` dpdklab
2024-03-01 0:30 ` dpdklab
2024-03-01 0:34 ` dpdklab
2024-03-02 2:29 ` dpdklab
2024-03-02 2:54 ` dpdklab
2024-03-02 3:09 ` 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=20240228170338.29EE8122320@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).