automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw153005 [patch v6 6/6] bus/vmbus: set event for channel without monitoring support
Date: Wed, 16 Apr 2025 22:58:01 +0200 (CEST)	[thread overview]
Message-ID: <20250416205801.70EC7123F9E@dpdk.org> (raw)
In-Reply-To: <1744837038-5387-7-git-send-email-longli@linuxonhyperv.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153005

_coding style issues_


ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#78: FILE: drivers/bus/vmbus/vmbus_channel.c:31:
+	RTE_ATOMIC(uint32_t) *int_addr;
 	                     ^

total: 1 errors, 0 warnings, 35 lines checked

  parent reply	other threads:[~2025-04-16 20:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1744837038-5387-7-git-send-email-longli@linuxonhyperv.com>
2025-04-16 20:31 ` |SUCCESS| pw153000-153005 " qemudev
2025-04-16 20:35 ` qemudev
2025-04-16 20:58 ` checkpatch [this message]
2025-04-16 21:35 ` |SUCCESS| pw153000-153005 [PATCH] [v6,6/6] bus/vmbus: set event for dpdklab
2025-04-16 21:35 ` dpdklab
2025-04-16 21:36 ` dpdklab
2025-04-16 21:39 ` |PENDING| " dpdklab
2025-04-16 21:41 ` dpdklab
2025-04-16 21:46 ` |SUCCESS| " dpdklab
2025-04-16 21:50 ` dpdklab
2025-04-16 21:52 ` |PENDING| " dpdklab
2025-04-16 21:53 ` |SUCCESS| " dpdklab
2025-04-16 21:58 ` |PENDING| " dpdklab
2025-04-16 22:00 ` |SUCCESS| " dpdklab
2025-04-16 22:02 ` dpdklab
2025-04-16 22:11 ` dpdklab
2025-04-16 22:13 ` dpdklab
2025-04-16 22:22 ` dpdklab
2025-04-16 22:30 ` dpdklab
2025-04-16 22:33 ` |WARNING| " dpdklab
2025-04-16 22:35 ` dpdklab
2025-04-16 22:35 ` dpdklab
2025-04-16 22:45 ` |SUCCESS| " dpdklab
2025-04-16 22:47 ` dpdklab
2025-04-16 23:04 ` dpdklab
2025-04-16 23:21 ` dpdklab
2025-04-16 23:36 ` dpdklab
2025-04-17  0:23 ` 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=20250416205801.70EC7123F9E@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).