From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw131938 [PATCH] maintainers: update for hns3
Date: Tue, 26 Sep 2023 12:08:26 +0200 (CEST) [thread overview]
Message-ID: <20230926100826.6625A120999@dpdk.org> (raw)
In-Reply-To: <20230926100405.58958-1-haijie1@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/131938
_coding style OK_
next prev parent reply other threads:[~2023-09-26 10:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230926100405.58958-1-haijie1@huawei.com>
2023-09-26 9:50 ` qemudev
2023-09-26 9:54 ` qemudev
2023-09-26 10:08 ` checkpatch [this message]
2023-09-26 10:59 ` 0-day Robot
2023-09-26 18:39 dpdklab
2023-09-26 18:43 dpdklab
2023-09-26 18:44 dpdklab
2023-09-26 18:45 dpdklab
2023-09-26 18:49 dpdklab
2023-09-26 18:50 dpdklab
2023-09-26 18:55 dpdklab
2023-09-26 18:55 dpdklab
2023-09-26 19:06 dpdklab
2023-09-26 19:16 dpdklab
2023-09-26 19:38 dpdklab
2023-09-26 19:40 dpdklab
2023-09-26 20:13 dpdklab
2023-09-26 20:14 dpdklab
2023-09-26 20:15 dpdklab
2023-09-26 20:15 dpdklab
2023-09-26 20:16 dpdklab
2023-09-26 20:16 dpdklab
2023-09-26 20:16 dpdklab
2023-09-26 20:17 dpdklab
2023-09-26 20:18 dpdklab
2023-09-26 20:18 dpdklab
2023-09-26 20:19 dpdklab
2023-09-26 20:21 dpdklab
2023-09-26 20:23 dpdklab
2023-09-26 20:24 dpdklab
2023-09-26 20:26 dpdklab
2023-09-26 20:28 dpdklab
2023-09-26 20:28 dpdklab
2023-09-26 20:29 dpdklab
2023-09-26 20:31 dpdklab
2023-09-26 20:45 dpdklab
2023-09-26 21:17 dpdklab
2023-09-26 21:19 dpdklab
2023-09-26 21:20 dpdklab
2023-09-26 21:36 dpdklab
2023-09-26 21:39 dpdklab
2023-09-26 21:45 dpdklab
2023-09-26 21:45 dpdklab
2023-09-26 21:47 dpdklab
2023-09-26 21:51 dpdklab
2023-09-26 21:52 dpdklab
2023-09-26 21:53 dpdklab
2023-09-26 21:55 dpdklab
2023-09-26 21:57 dpdklab
2023-09-26 21:57 dpdklab
2023-09-26 22:00 dpdklab
2023-09-27 2: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=20230926100826.6625A120999@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).