From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC version
Date: Mon, 11 Mar 2024 02:55:54 +0100 (CET) [thread overview]
Message-ID: <20240311015554.700E61223EF@dpdk.org> (raw)
In-Reply-To: <20240311015414.2514845-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138144
_coding style OK_
next prev parent reply other threads:[~2024-03-11 1:55 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311015414.2514845-1-chaoyong.he@corigine.com>
2024-03-11 1:33 ` qemudev
2024-03-11 1:38 ` qemudev
2024-03-11 1:55 ` checkpatch [this message]
2024-03-11 2:28 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC versio dpdklab
2024-03-11 2:29 ` dpdklab
2024-03-11 2:30 ` dpdklab
2024-03-11 2:33 ` dpdklab
2024-03-11 2:35 ` dpdklab
2024-03-11 2:35 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:36 ` dpdklab
2024-03-11 2:37 ` dpdklab
2024-03-11 2:37 ` dpdklab
2024-03-11 2:37 ` dpdklab
2024-03-11 2:37 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:38 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:39 ` dpdklab
2024-03-11 2:40 ` dpdklab
2024-03-11 2:40 ` dpdklab
2024-03-11 2:40 ` dpdklab
2024-03-11 2:40 ` dpdklab
2024-03-11 2:40 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:41 ` dpdklab
2024-03-11 2:42 ` dpdklab
2024-03-11 2:42 ` dpdklab
2024-03-11 2:42 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC version 0-day Robot
2024-03-11 2:43 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC versio dpdklab
2024-03-11 2:43 ` dpdklab
2024-03-11 2:44 ` dpdklab
2024-03-11 2:44 ` dpdklab
2024-03-11 2:44 ` dpdklab
2024-03-11 2:45 ` dpdklab
2024-03-11 2:46 ` dpdklab
2024-03-11 2:47 ` dpdklab
2024-03-11 2:47 ` dpdklab
2024-03-11 2:47 ` dpdklab
2024-03-11 2:48 ` dpdklab
2024-03-11 2:49 ` dpdklab
2024-03-11 2:49 ` dpdklab
2024-03-11 2:49 ` dpdklab
2024-03-11 2:50 ` dpdklab
2024-03-11 2:51 ` dpdklab
2024-03-11 2:52 ` dpdklab
2024-03-11 2:53 ` dpdklab
2024-03-11 2:54 ` dpdklab
2024-03-11 2:57 ` dpdklab
2024-03-11 3:29 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 12:27 ` 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=20240311015554.700E61223EF@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).