From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Guo Jia <jia.guo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw28310 [PATCH v4 1/2] eal: add uevent monitor for hot plug
Date: Sun, 3 Sep 2017 17:50:17 +0200 (CEST) [thread overview]
Message-ID: <20170903155017.E601E7CC0@dpdk.org> (raw)
In-Reply-To: <1504453785-15735-2-git-send-email-jia.guo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/28310
_coding style issues_
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#224: FILE: lib/librte_eal/common/eal_common_dev.c:385:
+ return -1;
+ } else
WARNING:LONG_LINE: line over 90 characters
#699: FILE: lib/librte_eal/linuxapp/eal/eal_pci_uio.c:258:
+ map_address = pci_map_private_resource(dev->mem_resource[i].addr, 0,
WARNING:LONG_LINE_COMMENT: line over 90 characters
#724: FILE: lib/librte_eal/linuxapp/eal/eal_pci_uio.c:283:
+ /*remap the resource to be fake before removal processing */
WARNING:LONG_LINE: line over 90 characters
#727: FILE: lib/librte_eal/linuxapp/eal/eal_pci_uio.c:286:
+ _rte_eal_uev_callback_process(&dev->device, RTE_EAL_UEVENT_REMOVE, NULL, NULL);
total: 0 errors, 4 warnings, 664 lines checked
parent reply other threads:[~2017-09-03 15:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1504453785-15735-2-git-send-email-jia.guo@intel.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=20170903155017.E601E7CC0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jia.guo@intel.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).