From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Xiao Wang <xiao.w.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw38147 [PATCH v7 2/5] vfio: add multi container support
Date: Sun, 15 Apr 2018 17:35:16 +0200 (CEST) [thread overview]
Message-ID: <20180415153516.BA6811B61F@dpdk.org> (raw)
In-Reply-To: <20180415153349.62105-3-xiao.w.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/38147
_coding style issues_
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#46: FILE: lib/librte_eal/bsdapp/eal/eal.c:772:
+int rte_vfio_container_create(void);
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#47: FILE: lib/librte_eal/bsdapp/eal/eal.c:773:
+int rte_vfio_container_destroy(int container_fd);
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#48: FILE: lib/librte_eal/bsdapp/eal/eal.c:774:
+int rte_vfio_bind_group(int container_fd, int iommu_group_no);
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#49: FILE: lib/librte_eal/bsdapp/eal/eal.c:775:
+int rte_vfio_unbind_group(int container_fd, int iommu_group_no);
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#50: FILE: lib/librte_eal/bsdapp/eal/eal.c:776:
+int rte_vfio_container_dma_map(int container_fd, uint64_t vaddr,
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#52: FILE: lib/librte_eal/bsdapp/eal/eal.c:778:
+int rte_vfio_container_dma_unmap(int container_fd, uint64_t vaddr,
total: 0 errors, 6 warnings, 525 lines checked
parent reply other threads:[~2018-04-15 15:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180415153349.62105-3-xiao.w.wang@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=20180415153516.BA6811B61F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xiao.w.wang@intel.com \
/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).