From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: priikone@iki.fi
Subject: |WARNING| pw154620 [PATCH] bus/pci: fix automatic interrupt type selection
Date: Fri, 20 Jun 2025 13:46:43 +0200 (CEST) [thread overview]
Message-ID: <20250620114643.A32711252C6@dpdk.org> (raw)
In-Reply-To: <8f5b22d3bedef793bf489c230b52b145@iki.fi>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154620
_coding style issues_
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#67: FILE: drivers/bus/pci/linux/pci_vfio.c:236:
*dev, int vfio_dev_fd)
ERROR:CODE_INDENT: code indent should use tabs where possible
#71: FILE: drivers/bus/pci/linux/pci_vfio.c:240:
+ /* If no vectors, try another one */$
ERROR:CODE_INDENT: code indent should use tabs where possible
#72: FILE: drivers/bus/pci/linux/pci_vfio.c:241:
+ if (irq.count == 0)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#72: FILE: drivers/bus/pci/linux/pci_vfio.c:241:
+ if (irq.count == 0)$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (15, 23)
#72: FILE: drivers/bus/pci/linux/pci_vfio.c:241:
+ if (irq.count == 0)
+ continue;
ERROR:CODE_INDENT: code indent should use tabs where possible
#73: FILE: drivers/bus/pci/linux/pci_vfio.c:242:
+ continue;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#73: FILE: drivers/bus/pci/linux/pci_vfio.c:242:
+ continue;$
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: priikone@iki.fi' != 'Signed-off-by: Pekka Riikonen <priikone@iki.fi>'
total: 4 errors, 4 warnings, 10 lines checked
prev parent reply other threads:[~2025-06-20 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f5b22d3bedef793bf489c230b52b145@iki.fi>
2025-06-20 11:14 ` qemudev
2025-06-20 11:46 ` checkpatch [this message]
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=20250620114643.A32711252C6@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=priikone@iki.fi \
--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).