From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw140337 [PATCH 2/2] net/nfp: support new firmware name scheme
Date: Tue, 28 May 2024 03:30:26 +0200 (CEST) [thread overview]
Message-ID: <20240528013026.E43F412367B@dpdk.org> (raw)
In-Reply-To: <20240528012933.2345436-3-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/140337
_coding style OK_
next prev parent reply other threads:[~2024-05-28 1:30 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528012933.2345436-3-chaoyong.he@corigine.com>
2024-05-28 1:03 ` |SUCCESS| pw140336-140337 " qemudev
2024-05-28 1:07 ` qemudev
2024-05-28 1:30 ` checkpatch [this message]
2024-05-28 2:05 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28 2:05 ` dpdklab
2024-05-28 2:06 ` dpdklab
2024-05-28 2:06 ` dpdklab
2024-05-28 2:06 ` dpdklab
2024-05-28 2:07 ` dpdklab
2024-05-28 2:07 ` dpdklab
2024-05-28 2:08 ` dpdklab
2024-05-28 2:08 ` dpdklab
2024-05-28 2:08 ` dpdklab
2024-05-28 2:09 ` dpdklab
2024-05-28 2:09 ` dpdklab
2024-05-28 2:09 ` dpdklab
2024-05-28 2:10 ` dpdklab
2024-05-28 2:10 ` dpdklab
2024-05-28 2:10 ` dpdklab
2024-05-28 2:10 ` dpdklab
2024-05-28 2:11 ` dpdklab
2024-05-28 2:11 ` dpdklab
2024-05-28 2:11 ` dpdklab
2024-05-28 2:12 ` dpdklab
2024-05-28 2:12 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:13 ` dpdklab
2024-05-28 2:14 ` dpdklab
2024-05-28 2:14 ` dpdklab
2024-05-28 2:14 ` dpdklab
2024-05-28 2:14 ` dpdklab
2024-05-28 2:14 ` dpdklab
2024-05-28 2:15 ` dpdklab
2024-05-28 2:15 ` dpdklab
2024-05-28 2:17 ` dpdklab
2024-05-28 2:17 ` dpdklab
2024-05-28 2:23 ` |SUCCESS| pw140337 [PATCH 2/2] net/nfp: support new firmware name scheme 0-day Robot
2024-05-28 2:27 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:28 ` dpdklab
2024-05-28 2:29 ` dpdklab
2024-05-28 2:31 ` dpdklab
2024-05-28 2:31 ` dpdklab
2024-05-28 2:31 ` dpdklab
2024-05-28 2:32 ` dpdklab
2024-05-28 2:32 ` dpdklab
2024-05-28 2:32 ` dpdklab
2024-05-28 2:32 ` dpdklab
2024-05-28 2:33 ` dpdklab
2024-05-28 2:33 ` dpdklab
2024-05-28 2:33 ` dpdklab
2024-05-28 2:58 ` dpdklab
2024-05-28 2:59 ` dpdklab
2024-05-28 2:59 ` dpdklab
2024-05-28 2:59 ` dpdklab
2024-05-28 3:00 ` dpdklab
2024-05-28 3:00 ` dpdklab
2024-05-28 3:00 ` dpdklab
2024-05-28 3:01 ` dpdklab
2024-05-28 3:01 ` dpdklab
2024-05-28 3:01 ` dpdklab
2024-05-28 3:02 ` dpdklab
2024-05-28 3:05 ` dpdklab
2024-05-28 3:07 ` dpdklab
2024-05-28 3:07 ` dpdklab
2024-05-28 3:08 ` dpdklab
2024-05-28 3:08 ` dpdklab
2024-05-28 3:10 ` dpdklab
2024-05-28 3:10 ` dpdklab
2024-05-28 3:10 ` dpdklab
2024-05-28 3:11 ` dpdklab
2024-05-28 5:28 ` dpdklab
2024-05-28 5:39 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22: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=20240528013026.E43F412367B@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).