From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138116 [PATCH] net/mlx5: fix the timing of releasing drop action
Date: Fri, 8 Mar 2024 04:23:41 +0100 (CET) [thread overview]
Message-ID: <20240308032341.A3CC71223EF@dpdk.org> (raw)
In-Reply-To: <20240308032237.315106-1-bingz@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138116
_coding style OK_
next prev parent reply other threads:[~2024-03-08 3:23 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308032237.315106-1-bingz@nvidia.com>
2024-03-08 3:00 ` qemudev
2024-03-08 3:05 ` qemudev
2024-03-08 3:23 ` checkpatch [this message]
2024-03-08 4:24 ` 0-day Robot
2024-03-08 7:49 ` |SUCCESS| pw138116 [PATCH] net/mlx5: fix the timing of releasing dro dpdklab
2024-03-08 7:53 ` dpdklab
2024-03-08 7:54 ` dpdklab
2024-03-08 7:56 ` dpdklab
2024-03-08 7:57 ` dpdklab
2024-03-08 8:41 ` dpdklab
2024-03-08 8:42 ` dpdklab
2024-03-08 8:43 ` dpdklab
2024-03-08 8:48 ` dpdklab
2024-03-08 8:48 ` dpdklab
2024-03-08 8:50 ` dpdklab
2024-03-08 8:51 ` dpdklab
2024-03-08 8:51 ` dpdklab
2024-03-08 8:51 ` dpdklab
2024-03-08 8:52 ` dpdklab
2024-03-08 8:52 ` dpdklab
2024-03-08 8:53 ` dpdklab
2024-03-08 8:53 ` dpdklab
2024-03-08 8:53 ` dpdklab
2024-03-08 8:56 ` dpdklab
2024-03-08 8:56 ` dpdklab
2024-03-08 8:57 ` dpdklab
2024-03-08 8:58 ` dpdklab
2024-03-08 8:58 ` dpdklab
2024-03-08 8:59 ` dpdklab
2024-03-08 8:59 ` dpdklab
2024-03-08 8:59 ` dpdklab
2024-03-08 9:00 ` dpdklab
2024-03-08 9:00 ` dpdklab
2024-03-08 9:01 ` dpdklab
2024-03-08 9:02 ` dpdklab
2024-03-08 9:02 ` dpdklab
2024-03-08 9:03 ` dpdklab
2024-03-08 9:03 ` dpdklab
2024-03-08 9:03 ` dpdklab
2024-03-08 9:03 ` dpdklab
2024-03-08 9:04 ` dpdklab
2024-03-08 9:04 ` dpdklab
2024-03-08 9:04 ` dpdklab
2024-03-08 9:04 ` dpdklab
2024-03-08 9:04 ` dpdklab
2024-03-08 9:05 ` dpdklab
2024-03-08 9:05 ` dpdklab
2024-03-08 9:06 ` dpdklab
2024-03-08 9:06 ` dpdklab
2024-03-08 9:10 ` dpdklab
2024-03-08 9:10 ` dpdklab
2024-03-08 9:11 ` dpdklab
2024-03-08 9:12 ` dpdklab
2024-03-08 9:13 ` dpdklab
2024-03-08 9:13 ` dpdklab
2024-03-08 9:13 ` dpdklab
2024-03-08 9:14 ` dpdklab
2024-03-08 9:15 ` dpdklab
2024-03-08 9:15 ` dpdklab
2024-03-08 9:16 ` dpdklab
2024-03-08 9:16 ` dpdklab
2024-03-08 9:17 ` dpdklab
2024-03-08 9:17 ` dpdklab
2024-03-08 9:18 ` dpdklab
2024-03-08 9:23 ` dpdklab
2024-03-08 9:24 ` dpdklab
2024-03-08 9:26 ` dpdklab
2024-03-08 10:07 ` dpdklab
2024-03-08 10:57 ` dpdklab
2024-03-08 12:12 ` dpdklab
2024-03-08 12:14 ` dpdklab
2024-03-08 12:25 ` dpdklab
2024-03-08 12:28 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 22:35 ` 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=20240308032341.A3CC71223EF@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).