From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw125059 [PATCH] bus/platform: probe devices without resources
Date: Mon, 13 Mar 2023 08:09:13 +0100 (CET) [thread overview]
Message-ID: <20230313070913.1AF781209C6@dpdk.org> (raw)
In-Reply-To: <20230313070735.2555186-1-tduszynski@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/125059
_coding style OK_
next prev parent reply other threads:[~2023-03-13 7:09 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230313070735.2555186-1-tduszynski@marvell.com>
2023-03-13 6:56 ` qemudev
2023-03-13 7:00 ` qemudev
2023-03-13 7:09 ` checkpatch [this message]
2023-03-13 9:19 ` 0-day Robot
2023-03-13 8:38 dpdklab
2023-03-13 8:55 dpdklab
2023-03-13 8:57 dpdklab
2023-03-13 9:08 dpdklab
2023-03-13 9:17 dpdklab
2023-03-13 9:37 dpdklab
2023-03-13 9:40 dpdklab
2023-03-13 9:43 dpdklab
2023-03-13 9:52 dpdklab
2023-03-13 9:55 dpdklab
2023-03-13 9:58 dpdklab
2023-03-13 10:04 dpdklab
2023-03-13 10:05 dpdklab
2023-03-13 10:05 dpdklab
2023-03-13 10:10 dpdklab
2023-03-13 10:11 dpdklab
2023-03-13 10:14 dpdklab
2023-03-13 10:16 dpdklab
2023-03-13 10:20 dpdklab
2023-03-13 10:25 dpdklab
2023-03-13 10:29 dpdklab
2023-03-13 10:31 dpdklab
2023-03-13 10:37 dpdklab
2023-03-13 10:39 dpdklab
2023-03-13 10:44 dpdklab
2023-03-13 10:47 dpdklab
2023-03-13 10:49 dpdklab
2023-03-13 11:01 dpdklab
2023-03-13 12:22 dpdklab
2023-03-13 17:05 dpdklab
2023-03-13 17:12 dpdklab
2023-03-13 21:43 dpdklab
2023-03-13 21:46 dpdklab
2023-03-13 21:54 dpdklab
2023-03-13 21:54 dpdklab
2023-03-13 21:57 dpdklab
2023-03-13 21:57 dpdklab
2023-03-13 21:58 dpdklab
2023-03-13 21:59 dpdklab
2023-03-13 22:00 dpdklab
2023-03-13 22:06 dpdklab
2023-03-13 22:09 dpdklab
2023-03-13 22:16 dpdklab
2023-03-13 22:22 dpdklab
2023-03-13 22:25 dpdklab
2023-03-13 23:10 dpdklab
2023-03-13 23:11 dpdklab
2023-03-14 18:33 dpdklab
2023-03-14 19:43 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=20230313070913.1AF781209C6@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).