From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141947 [PATCH 2/2] net/cnxk: avoid NPC Rx and MCAM entries disable
Date: Thu, 27 Jun 2024 11:09:41 +0200 (CEST) [thread overview]
Message-ID: <20240627090941.53D15128144@dpdk.org> (raw)
In-Reply-To: <20240627090859.2860207-2-rbhansali@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141947
_coding style OK_
next prev parent reply other threads:[~2024-06-27 9:10 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240627090859.2860207-2-rbhansali@marvell.com>
2024-06-27 8:43 ` |SUCCESS| pw141946-141947 " qemudev
2024-06-27 8:47 ` qemudev
2024-06-27 9:09 ` checkpatch [this message]
2024-06-27 10:06 ` |SUCCESS| pw141947 " 0-day Robot
2024-06-27 13:49 ` |SUCCESS| pw141946-141947 [PATCH] [2/2] net/cnxk: avoid NPC Rx and M dpdklab
2024-06-27 14:17 ` dpdklab
2024-06-27 14:29 ` dpdklab
2024-06-27 14:36 ` dpdklab
2024-06-27 14:48 ` dpdklab
2024-06-27 15:14 ` dpdklab
2024-06-27 15:22 ` dpdklab
2024-06-27 15:37 ` |PENDING| " dpdklab
2024-06-27 15:41 ` dpdklab
2024-06-27 15:42 ` dpdklab
2024-06-27 15:46 ` |SUCCESS| " dpdklab
2024-06-27 15:50 ` |PENDING| " dpdklab
2024-06-27 15:51 ` dpdklab
2024-06-27 16:00 ` |SUCCESS| " dpdklab
2024-06-27 16:07 ` dpdklab
2024-06-27 16:09 ` |PENDING| " dpdklab
2024-06-27 16:10 ` dpdklab
2024-06-27 16:11 ` dpdklab
2024-06-27 16:14 ` dpdklab
2024-06-27 16:15 ` dpdklab
2024-06-27 16:20 ` dpdklab
2024-06-27 16:21 ` |SUCCESS| " dpdklab
2024-06-27 16:23 ` dpdklab
2024-06-27 16:25 ` |PENDING| " dpdklab
2024-06-27 16:27 ` |SUCCESS| " dpdklab
2024-06-27 16:32 ` dpdklab
2024-06-27 16:32 ` |PENDING| " dpdklab
2024-06-27 16:34 ` dpdklab
2024-06-27 16:37 ` |SUCCESS| " dpdklab
2024-06-27 16:40 ` |PENDING| " dpdklab
2024-06-27 16:47 ` |SUCCESS| " dpdklab
2024-06-27 16:57 ` dpdklab
2024-06-27 17:35 ` dpdklab
2024-06-27 18:52 ` dpdklab
2024-06-27 18:52 ` dpdklab
2024-06-27 18:55 ` dpdklab
2024-06-27 18:58 ` dpdklab
2024-06-27 19:05 ` dpdklab
2024-06-27 19:07 ` dpdklab
2024-06-27 19:22 ` dpdklab
2024-06-27 19:34 ` dpdklab
2024-06-27 21:44 ` dpdklab
2024-06-27 23:00 ` dpdklab
2024-06-27 23:13 ` dpdklab
2024-06-27 23:20 ` dpdklab
2024-06-27 23:23 ` dpdklab
2024-06-27 23:24 ` dpdklab
2024-06-27 23:24 ` dpdklab
2024-06-27 23:26 ` dpdklab
2024-06-27 23:27 ` dpdklab
2024-06-27 23:28 ` dpdklab
2024-06-27 23:31 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:36 ` dpdklab
2024-06-27 23:39 ` dpdklab
2024-06-27 23:39 ` dpdklab
2024-06-27 23:40 ` dpdklab
2024-06-27 23:40 ` dpdklab
2024-06-27 23:43 ` dpdklab
2024-06-27 23:44 ` dpdklab
2024-06-27 23:44 ` dpdklab
2024-06-27 23:49 ` dpdklab
2024-06-27 23:49 ` dpdklab
2024-06-27 23:50 ` dpdklab
2024-06-27 23:51 ` dpdklab
2024-06-27 23:51 ` dpdklab
2024-06-27 23:51 ` dpdklab
2024-06-27 23:52 ` dpdklab
2024-06-27 23:53 ` dpdklab
2024-06-27 23:54 ` dpdklab
2024-06-27 23:54 ` dpdklab
2024-06-27 23:54 ` dpdklab
2024-06-27 23:54 ` dpdklab
2024-06-27 23:55 ` dpdklab
2024-06-27 23:56 ` dpdklab
2024-06-27 23:56 ` dpdklab
2024-06-27 23:58 ` dpdklab
2024-06-27 23:58 ` dpdklab
2024-06-28 0:00 ` dpdklab
2024-06-28 0:02 ` dpdklab
2024-06-28 0:03 ` dpdklab
2024-06-28 0:04 ` dpdklab
2024-06-28 0:05 ` dpdklab
2024-06-28 0:07 ` dpdklab
2024-06-28 0:07 ` dpdklab
2024-06-28 0:08 ` dpdklab
2024-06-28 0:14 ` dpdklab
2024-06-28 0:14 ` dpdklab
2024-06-28 0:15 ` dpdklab
2024-06-28 0:16 ` dpdklab
2024-06-28 0:17 ` dpdklab
2024-06-28 0:18 ` dpdklab
2024-06-28 0:18 ` dpdklab
2024-06-28 0:23 ` dpdklab
2024-06-28 0:26 ` dpdklab
2024-06-28 0:28 ` dpdklab
2024-06-28 0:31 ` dpdklab
2024-06-28 0:35 ` dpdklab
2024-06-28 5:46 ` dpdklab
2024-06-28 10:21 ` dpdklab
2024-06-28 10:38 ` dpdklab
2024-06-29 1:59 ` 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=20240627090941.53D15128144@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).