From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: dirk <dirk.lenz@ng4t.com>
Subject: [dpdk-test-report] |WARNING| pw58031 [PATCH 1/1] net/enic: enic driver doesn't work with 2nd process
Date: Tue, 27 Aug 2019 10:34:23 +0200 (CEST) [thread overview]
Message-ID: <20190827083423.042471C0D4@dpdk.org> (raw)
In-Reply-To: <20190827083306.5643-2-dirk.lenz@ng4t.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/58031
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#138: FILE: drivers/net/enic/enic_clsf.c:346:
+ struct enic *enic = pmd_priv(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#173: FILE: drivers/net/enic/enic_ethdev.c:167:
+ struct enic *enic = pmd_priv(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#462: FILE: drivers/net/enic/enic_main.c:35:
+ struct rte_pci_device *pdev = RTE_ETH_DEV_TO_PCI(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#464: FILE: drivers/net/enic/enic_main.c:37:
+ return pdev->id.device_id == PCI_DEVICE_ID_CISCO_VIC_ENET_VF;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#602: FILE: drivers/net/enic/enic_main.c:533:
+ struct enic *enic = pmd_priv(eth_dev);$
WARNING:TABSTOP: Statements should start on a tabstop
#679: FILE: drivers/net/enic/enic_main.c:647:
+ struct rte_pci_device *pdev = RTE_ETH_DEV_TO_PCI(eth_dev);
ERROR:CODE_INDENT: code indent should use tabs where possible
#682: FILE: drivers/net/enic/enic_main.c:650:
+^I enic_intr_handler, (void *)eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#699: FILE: drivers/net/enic/enic_main.c:728:
+ struct enic *enic = pmd_priv(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#701: FILE: drivers/net/enic/enic_main.c:730:
+ vnic_wq_enable(&enic->wq[queue_idx]);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1005: FILE: drivers/net/enic/enic_main.c:1758:
+ struct enic *enic = pmd_priv(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1006: FILE: drivers/net/enic/enic_main.c:1759:
+ struct rte_pci_device *pdev = RTE_ETH_DEV_TO_PCI(eth_dev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1039: FILE: drivers/net/enic/enic_res.c:26:
+ struct enic *enic = pmd_priv(eth_dev);$
total: 1 errors, 12 warnings, 0 checks, 975 lines checked
parent reply other threads:[~2019-08-27 8:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190827083306.5643-2-dirk.lenz@ng4t.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=20190827083423.042471C0D4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dirk.lenz@ng4t.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).