From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw150559 [PATCH 4/4] net/netvsc: cache device parameters for hot plug events
Date: Tue, 28 Jan 2025 02:34:50 +0100 (CET) [thread overview]
Message-ID: <20250128013450.15763127005@dpdk.org> (raw)
In-Reply-To: <1738028106-25239-4-git-send-email-longli@linuxonhyperv.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/150559
_coding style OK_
next prev parent reply other threads:[~2025-01-28 1:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1738028106-25239-4-git-send-email-longli@linuxonhyperv.com>
2025-01-28 1:14 ` |SUCCESS| pw150556-150559 " qemudev
2025-01-28 1:18 ` qemudev
2025-01-28 1:34 ` checkpatch [this message]
2025-01-28 2:23 ` |FAILURE| pw150559 " 0-day Robot
2025-01-28 2:30 ` |PENDING| pw150556-150559 [PATCH] [4/4] net/netvsc: cache device par dpdklab
2025-01-28 2:31 ` |SUCCESS| " dpdklab
2025-01-28 2:33 ` |PENDING| " dpdklab
2025-01-28 2:33 ` |SUCCESS| " dpdklab
2025-01-28 2:35 ` dpdklab
2025-01-28 2:36 ` |FAILURE| " dpdklab
2025-01-28 2:37 ` dpdklab
2025-01-28 2:38 ` |SUCCESS| " dpdklab
2025-01-28 2:41 ` |FAILURE| " dpdklab
2025-01-28 2:41 ` dpdklab
2025-01-28 2:43 ` |SUCCESS| " dpdklab
2025-01-28 2:45 ` dpdklab
2025-01-28 2:49 ` |FAILURE| " dpdklab
2025-01-28 2:51 ` dpdklab
2025-01-28 2:52 ` dpdklab
2025-01-28 2:53 ` dpdklab
2025-01-28 2:55 ` dpdklab
2025-01-28 2:55 ` dpdklab
2025-01-28 2:57 ` dpdklab
2025-01-28 2:59 ` |SUCCESS| " dpdklab
2025-01-28 3:01 ` |FAILURE| " dpdklab
2025-01-28 3:03 ` dpdklab
2025-01-28 3:06 ` dpdklab
2025-01-28 3:09 ` |WARNING| " dpdklab
2025-01-28 3:16 ` |FAILURE| " dpdklab
2025-01-28 3:22 ` |SUCCESS| " dpdklab
2025-01-28 3:49 ` |WARNING| " dpdklab
2025-01-28 3:49 ` |FAILURE| " dpdklab
2025-01-28 13:48 ` |WARNING| " dpdklab
2025-01-30 1:54 ` |SUCCESS| " 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=20250128013450.15763127005@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).