From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137658 [PATCH] net/mlx5: set correct priority for meter policy
Date: Fri, 1 Mar 2024 09:47:13 +0100 (CET) [thread overview]
Message-ID: <20240301084713.5E6EE12232A@dpdk.org> (raw)
In-Reply-To: <20240301084605.1652351-1-shunh@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137658
_coding style OK_
next prev parent reply other threads:[~2024-03-01 8:47 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301084605.1652351-1-shunh@nvidia.com>
2024-03-01 8:30 ` qemudev
2024-03-01 8:34 ` qemudev
2024-03-01 8:47 ` checkpatch [this message]
2024-03-01 9:45 ` 0-day Robot
2024-03-01 16:13 ` |SUCCESS| pw137658 [PATCH] net/mlx5: set correct priority for meter dpdklab
2024-03-01 16:40 ` |FAILURE| " dpdklab
2024-03-01 16:46 ` |SUCCESS| " dpdklab
2024-03-01 16:51 ` |FAILURE| " dpdklab
2024-03-01 17:14 ` |SUCCESS| " dpdklab
2024-03-01 17:17 ` dpdklab
2024-03-01 17:21 ` |FAILURE| " dpdklab
2024-03-01 17:25 ` |SUCCESS| " dpdklab
2024-03-01 17:29 ` dpdklab
2024-03-01 17:31 ` dpdklab
2024-03-01 17:33 ` dpdklab
2024-03-01 17:34 ` dpdklab
2024-03-01 17:35 ` dpdklab
2024-03-01 17:35 ` dpdklab
2024-03-01 17:36 ` dpdklab
2024-03-01 17:36 ` dpdklab
2024-03-01 17:38 ` dpdklab
2024-03-01 17:39 ` dpdklab
2024-03-01 19:32 ` dpdklab
2024-03-01 19:44 ` dpdklab
2024-03-01 19:45 ` dpdklab
2024-03-01 19:45 ` dpdklab
2024-03-01 19:49 ` dpdklab
2024-03-01 19:53 ` dpdklab
2024-03-01 19:53 ` dpdklab
2024-03-01 19:53 ` dpdklab
2024-03-01 19:53 ` dpdklab
2024-03-01 19:53 ` dpdklab
2024-03-01 19:54 ` dpdklab
2024-03-01 19:54 ` dpdklab
2024-03-01 19:57 ` dpdklab
2024-03-01 19:57 ` dpdklab
2024-03-01 19:57 ` dpdklab
2024-03-01 19:58 ` dpdklab
2024-03-01 19:58 ` dpdklab
2024-03-01 19:58 ` dpdklab
2024-03-01 19:59 ` dpdklab
2024-03-01 19:59 ` dpdklab
2024-03-01 19:59 ` dpdklab
2024-03-01 19:59 ` dpdklab
2024-03-01 20:00 ` dpdklab
2024-03-01 20:00 ` dpdklab
2024-03-01 20:00 ` dpdklab
2024-03-01 20:00 ` dpdklab
2024-03-01 20:01 ` dpdklab
2024-03-01 20:01 ` dpdklab
2024-03-01 20:01 ` dpdklab
2024-03-01 20:01 ` dpdklab
2024-03-01 20:03 ` dpdklab
2024-03-01 20:03 ` dpdklab
2024-03-01 20:08 ` dpdklab
2024-03-01 20:08 ` dpdklab
2024-03-01 20:08 ` dpdklab
2024-03-01 20:09 ` dpdklab
2024-03-01 20:09 ` dpdklab
2024-03-01 20:09 ` dpdklab
2024-03-01 20:10 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:48 ` dpdklab
2024-03-01 20:55 ` dpdklab
2024-03-01 21:01 ` dpdklab
2024-03-01 21:03 ` dpdklab
2024-03-01 21:04 ` dpdklab
2024-03-01 21:10 ` |FAILURE| " dpdklab
2024-03-01 21:13 ` |SUCCESS| " dpdklab
2024-03-01 21:37 ` dpdklab
2024-03-02 1:17 ` dpdklab
2024-03-02 1:25 ` dpdklab
2024-03-02 1:36 ` dpdklab
2024-03-02 22:31 ` dpdklab
2024-03-05 13:06 ` dpdklab
2024-03-05 13:51 ` dpdklab
2024-03-05 14:20 ` 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=20240301084713.5E6EE12232A@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).