From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw152779 [Patch v3 6/6] bus/vmbus: set event for channel without monitoring support
Date: Sat, 5 Apr 2025 02:37:05 +0200 (CEST) [thread overview]
Message-ID: <20250405003705.6CEEC1251A5@dpdk.org> (raw)
In-Reply-To: <1743813338-28238-7-git-send-email-longli@linuxonhyperv.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152779
_coding style issues_
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#77: FILE: drivers/bus/vmbus/vmbus_channel.c:30:
+ RTE_ATOMIC(uint32_t) *int_addr;
^
total: 1 errors, 0 warnings, 34 lines checked
next prev parent reply other threads:[~2025-04-05 0:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1743813338-28238-7-git-send-email-longli@linuxonhyperv.com>
2025-04-05 0:03 ` |SUCCESS| pw152774-152779 " qemudev
2025-04-05 0:07 ` qemudev
2025-04-05 0:37 ` checkpatch [this message]
2025-04-05 1:10 ` |SUCCESS| pw152774-152779 [PATCH] [v3,6/6] bus/vmbus: set event for dpdklab
2025-04-05 1:12 ` dpdklab
2025-04-05 1:15 ` dpdklab
2025-04-05 1:15 ` |PENDING| " dpdklab
2025-04-05 1:20 ` |WARNING| " dpdklab
2025-04-05 1:22 ` |SUCCESS| " dpdklab
2025-04-05 1:23 ` |PENDING| " dpdklab
2025-04-05 1:27 ` |SUCCESS| " dpdklab
2025-04-05 1:30 ` dpdklab
2025-04-05 1:31 ` |PENDING| " dpdklab
2025-04-05 1:32 ` |FAILURE| " dpdklab
2025-04-05 1:42 ` |FAILURE| pw152779 [Patch v3 6/6] bus/vmbus: set event for channel without monitoring support 0-day Robot
2025-04-05 1:43 ` |FAILURE| pw152774-152779 [PATCH] [v3,6/6] bus/vmbus: set event for dpdklab
2025-04-05 1:55 ` |SUCCESS| " dpdklab
2025-04-05 1:55 ` |FAILURE| " dpdklab
2025-04-05 1:58 ` |SUCCESS| " dpdklab
2025-04-05 2:03 ` |WARNING| " dpdklab
2025-04-05 2:21 ` |SUCCESS| " dpdklab
2025-04-05 3:00 ` dpdklab
2025-04-07 18:32 ` 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=20250405003705.6CEEC1251A5@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=longli@linuxonhyperv.com \
--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).