automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-test-report] |WARNING| [RFC PATCH 3/6] bus: add bus driver layer
Date: Thu, 17 Nov 2016 06:29:09 +0100 (CET)	[thread overview]
Message-ID: <20161117052909.16782590E@dpdk.org> (raw)
In-Reply-To: <1479360605-20558-4-git-send-email-shreyansh.jain@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'implmentation' may be misspelled - perhaps 'implementation'?
#140: 
 - This way, each bus implmentation would be within the drivers/* area and

ERROR:SPACING: space required after that ',' (ctx:VxV)
#380: FILE: bus/pci/linuxapp/pci_bus.c:93:
+	splitaddr.function = strchr(splitaddr.devid,'.');
 	                                           ^

ERROR:SPACING: spaces required around that '<' (ctx:VxV)
#417: FILE: bus/pci/linuxapp/pci_bus.c:130:
+	for (i = 0; i<PCI_MAX_RESOURCE; i++) {
 	             ^

ERROR:SPACING: space required after that ',' (ctx:VxV)
#445: FILE: bus/pci/linuxapp/pci_bus.c:158:
+pci_scan_one(const char *dirname, uint16_t domain, uint8_t bus,uint8_t devid,
                                                               ^

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#760: FILE: bus/pci/linuxapp/pci_bus.h:49:
+/**
+* Scan the content of the PCI bus, and the devices in the devices

total: 3 errors, 2 warnings, 546 lines checked

           reply	other threads:[~2016-11-17  5:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1479360605-20558-4-git-send-email-shreyansh.jain@nxp.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=20161117052909.16782590E@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=shreyansh.jain@nxp.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).