From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142394 [PATCH v8 21/21] net/ntnic: add physical layer control module
Date: Fri, 12 Jul 2024 17:56:30 +0200 (CEST) [thread overview]
Message-ID: <20240712155630.A4180128144@dpdk.org> (raw)
In-Reply-To: <20240712154737.1339646-21-sil-plv@napatech.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142394
_coding style OK_
next parent reply other threads:[~2024-07-12 15:56 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240712154737.1339646-21-sil-plv@napatech.com>
2024-07-12 15:56 ` checkpatch [this message]
2024-07-12 19:44 ` 0-day Robot
2024-07-13 3:49 ` |SUCCESS| pw142375-142394 [PATCH] [v8,21/21] net/ntnic: add physical dpdklab
2024-07-13 3:53 ` dpdklab
2024-07-13 3:57 ` dpdklab
2024-07-13 3:57 ` dpdklab
2024-07-13 3:58 ` |PENDING| " dpdklab
2024-07-13 4:03 ` dpdklab
2024-07-13 4:06 ` dpdklab
2024-07-13 4:06 ` |SUCCESS| " dpdklab
2024-07-13 4:07 ` |PENDING| " dpdklab
2024-07-13 4:10 ` |SUCCESS| " dpdklab
2024-07-13 4:11 ` dpdklab
2024-07-13 4:12 ` dpdklab
2024-07-13 4:12 ` dpdklab
2024-07-13 4:13 ` dpdklab
2024-07-13 4:14 ` dpdklab
2024-07-13 4:20 ` |PENDING| " dpdklab
2024-07-13 4:22 ` dpdklab
2024-07-13 4:22 ` dpdklab
2024-07-13 4:28 ` dpdklab
2024-07-13 4:28 ` dpdklab
2024-07-13 4:28 ` dpdklab
2024-07-13 4:28 ` |SUCCESS| " dpdklab
2024-07-13 4:29 ` |PENDING| " dpdklab
2024-07-13 4:29 ` dpdklab
2024-07-13 4:31 ` dpdklab
2024-07-13 4:34 ` dpdklab
2024-07-13 4:34 ` dpdklab
2024-07-13 4:37 ` dpdklab
2024-07-13 4:39 ` dpdklab
2024-07-13 4:40 ` dpdklab
2024-07-13 4:42 ` dpdklab
2024-07-13 4:42 ` dpdklab
2024-07-13 4:45 ` dpdklab
2024-07-13 4:45 ` dpdklab
2024-07-13 4:47 ` dpdklab
2024-07-13 4:47 ` dpdklab
2024-07-13 4:52 ` dpdklab
2024-07-13 4:54 ` dpdklab
2024-07-13 4:57 ` dpdklab
2024-07-13 4:58 ` dpdklab
2024-07-13 5:00 ` dpdklab
2024-07-13 5:00 ` dpdklab
2024-07-13 5:01 ` dpdklab
2024-07-13 5:01 ` dpdklab
2024-07-13 5:03 ` dpdklab
2024-07-13 5:03 ` dpdklab
2024-07-13 5:03 ` dpdklab
2024-07-13 5:03 ` dpdklab
2024-07-13 5:04 ` dpdklab
2024-07-13 5:04 ` dpdklab
2024-07-13 5:04 ` dpdklab
2024-07-13 5:06 ` dpdklab
2024-07-13 5:06 ` dpdklab
2024-07-13 5:07 ` dpdklab
2024-07-13 5:07 ` dpdklab
2024-07-13 5:07 ` dpdklab
2024-07-13 5:09 ` dpdklab
2024-07-13 5:10 ` dpdklab
2024-07-13 5:11 ` dpdklab
2024-07-13 5:14 ` dpdklab
2024-07-13 5:14 ` dpdklab
2024-07-13 5:16 ` dpdklab
2024-07-13 5:16 ` dpdklab
2024-07-13 5:17 ` dpdklab
2024-07-13 5:17 ` dpdklab
2024-07-13 5:17 ` dpdklab
2024-07-13 5:17 ` dpdklab
2024-07-13 5:18 ` dpdklab
2024-07-13 5:19 ` dpdklab
2024-07-13 5:23 ` dpdklab
2024-07-13 5:24 ` dpdklab
2024-07-13 5:24 ` dpdklab
2024-07-13 5:24 ` dpdklab
2024-07-13 5:28 ` |SUCCESS| " dpdklab
2024-07-13 5:28 ` dpdklab
2024-07-13 5:29 ` |PENDING| " dpdklab
2024-07-13 5:30 ` dpdklab
2024-07-13 5:33 ` dpdklab
2024-07-13 5:34 ` dpdklab
2024-07-13 5:35 ` dpdklab
2024-07-13 5:37 ` dpdklab
2024-07-13 5:39 ` dpdklab
2024-07-13 5:40 ` dpdklab
2024-07-13 5:41 ` dpdklab
2024-07-13 5:43 ` dpdklab
2024-07-13 5:43 ` dpdklab
2024-07-13 5:45 ` dpdklab
2024-07-13 5:49 ` dpdklab
2024-07-13 5:50 ` dpdklab
2024-07-13 5:50 ` dpdklab
2024-07-13 5:51 ` dpdklab
2024-07-13 5:52 ` dpdklab
2024-07-13 5:53 ` dpdklab
2024-07-13 5:55 ` dpdklab
2024-07-13 5:55 ` dpdklab
2024-07-13 5:56 ` dpdklab
2024-07-13 5:57 ` dpdklab
2024-07-13 6:00 ` |SUCCESS| " dpdklab
2024-07-13 6:04 ` |PENDING| " dpdklab
2024-07-13 6:07 ` dpdklab
2024-07-13 6:07 ` dpdklab
2024-07-13 6:12 ` |SUCCESS| " dpdklab
2024-07-13 6:16 ` dpdklab
2024-07-13 6:22 ` |PENDING| " dpdklab
2024-07-13 6:24 ` |SUCCESS| " dpdklab
2024-07-13 6:26 ` dpdklab
2024-07-13 6:26 ` dpdklab
2024-07-15 14:49 ` dpdklab
2024-07-15 14:53 ` dpdklab
2024-07-15 14:57 ` dpdklab
2024-07-15 15:28 ` dpdklab
2024-07-15 15:47 ` 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=20240712155630.A4180128144@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).