From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137657 [PATCH v2 3/3] net/nfp: add force reload firmware option
Date: Fri, 1 Mar 2024 09:45:30 +0100 (CET) [thread overview]
Message-ID: <20240301084530.48A2D12232A@dpdk.org> (raw)
In-Reply-To: <20240301084244.190484-4-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137657
_coding style OK_
next prev parent reply other threads:[~2024-03-01 8:45 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301084244.190484-4-chaoyong.he@corigine.com>
2024-03-01 8:35 ` |SUCCESS| pw137655-137657 " qemudev
2024-03-01 8:40 ` qemudev
2024-03-01 8:45 ` checkpatch [this message]
2024-03-01 9:45 ` |SUCCESS| pw137657 " 0-day Robot
2024-03-01 16:56 ` |SUCCESS| pw137655-137657 [PATCH] [v2,3/3] net/nfp: add force reload dpdklab
2024-03-01 17:08 ` dpdklab
2024-03-01 17:09 ` |FAILURE| " dpdklab
2024-03-01 17:13 ` dpdklab
2024-03-01 17:39 ` |SUCCESS| " dpdklab
2024-03-01 17:53 ` |FAILURE| " dpdklab
2024-03-01 17:54 ` |SUCCESS| " dpdklab
2024-03-01 17:56 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:58 ` dpdklab
2024-03-01 18:03 ` dpdklab
2024-03-01 18:05 ` dpdklab
2024-03-01 18:06 ` dpdklab
2024-03-01 18:07 ` dpdklab
2024-03-01 20:10 ` dpdklab
2024-03-01 20:11 ` dpdklab
2024-03-01 20:15 ` dpdklab
2024-03-01 20:15 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:18 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:20 ` dpdklab
2024-03-01 20:20 ` dpdklab
2024-03-01 20:21 ` dpdklab
2024-03-01 20:26 ` dpdklab
2024-03-01 20:27 ` dpdklab
2024-03-01 20:34 ` dpdklab
2024-03-01 20:35 ` dpdklab
2024-03-01 20:46 ` dpdklab
2024-03-01 20:48 ` dpdklab
2024-03-01 20:48 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:51 ` dpdklab
2024-03-01 20:54 ` dpdklab
2024-03-01 20:55 ` dpdklab
2024-03-01 20:55 ` dpdklab
2024-03-01 20:56 ` dpdklab
2024-03-01 20:59 ` dpdklab
2024-03-01 21:00 ` dpdklab
2024-03-01 21:00 ` dpdklab
2024-03-01 21:01 ` dpdklab
2024-03-01 21:02 ` dpdklab
2024-03-01 21:03 ` dpdklab
2024-03-01 21:04 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:06 ` dpdklab
2024-03-01 21:14 ` dpdklab
2024-03-01 21:14 ` dpdklab
2024-03-01 21:25 ` dpdklab
2024-03-01 21:31 ` dpdklab
2024-03-01 21:33 ` |FAILURE| " dpdklab
2024-03-01 21:35 ` |SUCCESS| " dpdklab
2024-03-01 21:49 ` dpdklab
2024-03-01 22:25 ` dpdklab
2024-03-01 22:27 ` dpdklab
2024-03-02 1:19 ` dpdklab
2024-03-02 1:21 ` dpdklab
2024-03-02 2:02 ` dpdklab
2024-03-02 22:58 ` dpdklab
2024-03-05 14:55 ` dpdklab
2024-03-05 15:33 ` dpdklab
2024-03-05 15:57 ` 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=20240301084530.48A2D12232A@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).