From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Vemula Venkatesh <venkatesh.vemula@intel.com>
Subject: |WARNING| pw156991 [PATCH v3] net/intel: add IDPF PCI class ID support
Date: Fri, 26 Sep 2025 10:48:41 +0200 (CEST) [thread overview]
Message-ID: <20250926084841.49340124240@dpdk.org> (raw)
In-Reply-To: <20250925174707.131821-1-venkatesh.vemula@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/156991
_coding style issues_
ERROR:SPACING: space required before the open brace '{'
#147: FILE: drivers/net/intel/idpf/idpf_common_device.c:392:
+ if (idpf_is_vf_device(hw)){
ERROR:SPACING: space prohibited before that close parenthesis ')'
#198: FILE: drivers/net/intel/idpf/idpf_common_device.h:63:
+IDPF_NETWORK_ETHERNET_PROGIF )
total: 2 errors, 0 warnings, 0 checks, 103 lines checked
next prev parent reply other threads:[~2025-09-26 8:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250925174707.131821-1-venkatesh.vemula@intel.com>
2025-09-26 8:15 ` |SUCCESS| " qemudev
2025-09-26 8:20 ` qemudev
2025-09-26 8:48 ` checkpatch [this message]
2025-09-26 9:37 ` |PENDING| pw156991 [PATCH] [v3] net/intel: add IDPF PCI class ID sup dpdklab
2025-09-26 9:39 ` |SUCCESS| " dpdklab
2025-09-26 9:43 ` dpdklab
2025-09-26 9:47 ` dpdklab
2025-09-26 10:02 ` |PENDING| " dpdklab
2025-09-26 10:04 ` |SUCCESS| " dpdklab
2025-09-26 10:07 ` |PENDING| " dpdklab
2025-09-26 10:12 ` |SUCCESS| " dpdklab
2025-09-26 10:14 ` |PENDING| " dpdklab
2025-09-26 10:26 ` |SUCCESS| pw156991 [PATCH v3] net/intel: add IDPF PCI class ID support 0-day Robot
2025-09-26 10:26 ` 0-day Robot
2025-09-26 10:29 ` |SUCCESS| pw156991 [PATCH] [v3] net/intel: add IDPF PCI class ID sup dpdklab
2025-09-26 10:30 ` dpdklab
2025-09-26 10:34 ` dpdklab
2025-09-26 10:35 ` dpdklab
2025-09-26 10:53 ` dpdklab
2025-09-26 11:18 ` dpdklab
2025-09-26 13:57 ` dpdklab
2025-09-26 23:20 ` dpdklab
2025-09-27 7:49 ` 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=20250926084841.49340124240@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=venkatesh.vemula@intel.com \
/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).