From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw132491 [PATCH] net/cpfl: update CP channel API
Date: Wed, 11 Oct 2023 05:21:51 +0200 (CEST) [thread overview]
Message-ID: <20231011032151.19F99120D36@dpdk.org> (raw)
In-Reply-To: <20231011114016.399609-1-beilei.xing@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/132491
_coding style OK_
next prev parent reply other threads:[~2023-10-11 3:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231011114016.399609-1-beilei.xing@intel.com>
2023-10-11 3:01 ` qemudev
2023-10-11 3:05 ` qemudev
2023-10-11 3:21 ` checkpatch [this message]
2023-10-11 8:44 dpdklab
2023-10-11 8:47 dpdklab
2023-10-11 8:47 dpdklab
2023-10-11 8:47 dpdklab
2023-10-11 8:51 dpdklab
2023-10-11 9:04 dpdklab
2023-10-11 9:13 dpdklab
2023-10-11 11:16 dpdklab
2023-10-11 11:18 dpdklab
2023-10-11 11:19 dpdklab
2023-10-11 12:10 dpdklab
2023-10-11 12:12 dpdklab
2023-10-11 12:13 dpdklab
2023-10-11 12:13 dpdklab
2023-10-11 12:14 dpdklab
2023-10-11 12:14 dpdklab
2023-10-11 12:30 dpdklab
2023-10-11 12:36 dpdklab
2023-10-11 12:51 dpdklab
2023-10-11 12:52 dpdklab
2023-10-11 12:54 dpdklab
2023-10-11 12:55 dpdklab
2023-10-11 12:55 dpdklab
2023-10-11 12:58 dpdklab
2023-10-11 12:59 dpdklab
2023-10-11 12:59 dpdklab
2023-10-11 13:02 dpdklab
2023-10-11 13:06 dpdklab
2023-10-11 13:07 dpdklab
2023-10-11 13:12 dpdklab
2023-10-11 13:14 dpdklab
2023-10-11 13:32 dpdklab
2023-10-11 13:32 dpdklab
2023-10-11 13:37 dpdklab
2023-10-11 13:37 dpdklab
2023-10-11 13:37 dpdklab
2023-10-11 13:37 dpdklab
2023-10-11 13:41 dpdklab
2023-10-11 13:42 dpdklab
2023-10-11 13:45 dpdklab
2023-10-11 13:53 dpdklab
2023-10-11 13:56 dpdklab
2023-10-11 13:57 dpdklab
2023-10-11 15:36 dpdklab
2023-10-12 10:49 dpdklab
2023-10-12 10:51 dpdklab
2023-10-12 10:53 dpdklab
2023-10-12 11:01 dpdklab
2023-10-12 18:41 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=20231011032151.19F99120D36@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).