From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141192 [PATCH v3 11/11] doc: update nfp document
Date: Mon, 17 Jun 2024 08:29:46 +0200 (CEST) [thread overview]
Message-ID: <20240617062946.F0957124124@dpdk.org> (raw)
In-Reply-To: <20240617062708.2932037-12-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141192
_coding style OK_
next prev parent reply other threads:[~2024-06-17 6:36 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240617062708.2932037-12-chaoyong.he@corigine.com>
2024-06-17 6:02 ` |SUCCESS| pw141182-141192 " qemudev
2024-06-17 6:06 ` qemudev
2024-06-17 6:29 ` checkpatch [this message]
2024-06-17 7:24 ` |SUCCESS| pw141192 " 0-day Robot
2024-06-17 11:42 ` |SUCCESS| pw141182-141192 [PATCH] [v3,11/11] doc: update nfp documen dpdklab
2024-06-17 11:42 ` dpdklab
2024-06-17 11:42 ` dpdklab
2024-06-17 11:43 ` dpdklab
2024-06-17 11:43 ` dpdklab
2024-06-17 12:01 ` dpdklab
2024-06-17 12:03 ` dpdklab
2024-06-17 12:04 ` dpdklab
2024-06-17 12:07 ` dpdklab
2024-06-17 12:08 ` dpdklab
2024-06-17 12:09 ` dpdklab
2024-06-17 12:17 ` dpdklab
2024-06-17 12:18 ` dpdklab
2024-06-17 12:18 ` dpdklab
2024-06-17 12:20 ` dpdklab
2024-06-17 12:24 ` dpdklab
2024-06-17 12:26 ` dpdklab
2024-06-17 12:26 ` dpdklab
2024-06-17 12:28 ` dpdklab
2024-06-17 12:28 ` dpdklab
2024-06-17 12:29 ` dpdklab
2024-06-17 12:34 ` dpdklab
2024-06-17 12:37 ` dpdklab
2024-06-17 12:38 ` dpdklab
2024-06-17 12:38 ` dpdklab
2024-06-17 12:39 ` dpdklab
2024-06-17 12:39 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:40 ` dpdklab
2024-06-17 12:41 ` dpdklab
2024-06-17 12:42 ` dpdklab
2024-06-17 12:42 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:43 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:44 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:45 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:46 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:47 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:48 ` dpdklab
2024-06-17 12:49 ` dpdklab
2024-06-17 12:49 ` dpdklab
2024-06-17 12:52 ` dpdklab
2024-06-17 12:53 ` dpdklab
2024-06-17 12:56 ` dpdklab
2024-06-17 12:57 ` dpdklab
2024-06-17 12:57 ` dpdklab
2024-06-17 12:59 ` dpdklab
2024-06-17 13:01 ` dpdklab
2024-06-17 13:02 ` dpdklab
2024-06-17 13:03 ` dpdklab
2024-06-17 13:08 ` dpdklab
2024-06-17 13:08 ` dpdklab
2024-06-17 13:09 ` dpdklab
2024-06-17 13:09 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:10 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:11 ` dpdklab
2024-06-17 13:12 ` dpdklab
2024-06-17 13:14 ` dpdklab
2024-06-17 13:15 ` dpdklab
2024-06-17 13:19 ` dpdklab
2024-06-17 13:19 ` dpdklab
2024-06-17 13:20 ` dpdklab
2024-06-17 13:21 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:24 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:25 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:26 ` dpdklab
2024-06-17 13:31 ` dpdklab
2024-06-17 13:32 ` dpdklab
2024-06-17 13:33 ` dpdklab
2024-06-17 13:33 ` dpdklab
2024-06-17 13:34 ` dpdklab
2024-06-17 13:35 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:36 ` dpdklab
2024-06-17 13:41 ` dpdklab
2024-06-17 13:46 ` dpdklab
2024-06-17 13:55 ` dpdklab
2024-06-17 14:04 ` dpdklab
2024-06-17 15:22 ` 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=20240617062946.F0957124124@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).