From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harman Kalra <hkalra@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw102699 [PATCH v5 4/6] drivers: remove direct access to interrupt handle
Date: Fri, 22 Oct 2021 22:52:37 +0200 (CEST) [thread overview]
Message-ID: <20211022205237.B8B20121E15@dpdk.org> (raw)
In-Reply-To: <20211022204934.132186-5-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/102699
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#960: FILE: drivers/bus/pci/linux/pci_uio.c:277:
+ if (pci_uio_set_bus_master(uio_cfg_fd)) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1214: FILE: drivers/bus/pci/linux/pci_vfio.c:1020:
+ if (pci_vfio_set_bus_master(vfio_dev_fd, false)) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2158: FILE: drivers/common/cnxk/roc_tim.c:203:
+ rc = tim_register_irq_priv(roc_tim, sso->pci_dev->intr_handle, ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2158: FILE: drivers/common/cnxk/roc_tim.c:203:
+ rc = tim_register_irq_priv(roc_tim, sso->pci_dev->intr_handle, ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2167: FILE: drivers/common/cnxk/roc_tim.c:226:
+ tim_unregister_irq_priv(roc_tim, sso->pci_dev->intr_handle, ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2167: FILE: drivers/common/cnxk/roc_tim.c:226:
+ tim_unregister_irq_priv(roc_tim, sso->pci_dev->intr_handle, ring_id,
CHECK:CAMELCASE: Avoid CamelCase: <intrIdx>
#7499: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:803:
+ tqd->conf.intrIdx =
total: 0 errors, 6 warnings, 7160 lines checked
parent reply other threads:[~2021-10-22 20:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20211022204934.132186-5-hkalra@marvell.com>]
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=20211022205237.B8B20121E15@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hkalra@marvell.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).