From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw32446 [PATCH RFC 23/23] eal/memalloc: register/unregister memory with VFIO when
Date: Tue, 19 Dec 2017 12:13:30 +0100 (CET) [thread overview]
Message-ID: <20171219111330.C2E851B015@dpdk.org> (raw)
In-Reply-To: <54308b0ede7578c3c0dd72d4404938e310f9db84.1513594170.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32446
_coding style issues_
WARNING:BRACES: braces {} are not necessary for single statement blocks
#40: FILE: lib/librte_eal/linuxapp/eal/eal_memalloc.c:264:
+ if (rte_iommu_dma_map(ms->addr_64, iova, size)) {
+ RTE_LOG(DEBUG, EAL, "Cannot register segment with VFIO
");
+ }
WARNING:BRACES: braces {} are not necessary for single statement blocks
#52: FILE: lib/librte_eal/linuxapp/eal/eal_memalloc.c:305:
+ if (rte_iommu_dma_unmap(ms->addr_64, ms->iova, ms->len)) {
+ RTE_LOG(DEBUG, EAL, "Cannot unregister segment with VFIO
");
+ }
total: 0 errors, 2 warnings, 29 lines checked
parent reply other threads:[~2017-12-19 11:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54308b0ede7578c3c0dd72d4404938e310f9db84.1513594170.git.anatoly.burakov@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=20171219111330.C2E851B015@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@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).