From: Yong Wang <yongwang@vmware.com>
To: <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>, Yong Wang <yongwang@vmware.com>
Subject: [dpdk-dev] [PATCH 2/2] vfio: fix coding style
Date: Thu, 7 Jul 2016 15:26:37 -0700 [thread overview]
Message-ID: <1467930397-39777-2-git-send-email-yongwang@vmware.com> (raw)
In-Reply-To: <1467930397-39777-1-git-send-email-yongwang@vmware.com>
Signed-off-by: Yong Wang <yongwang@vmware.com>
---
lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
index 3729c35..6492216 100644
--- a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
+++ b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
@@ -274,7 +274,8 @@ pci_vfio_set_bus_master(int dev_fd)
/* pick IOMMU type. returns a pointer to vfio_iommu_type or NULL for error */
static const struct vfio_iommu_type *
-pci_vfio_set_iommu_type(int vfio_container_fd) {
+pci_vfio_set_iommu_type(int vfio_container_fd)
+{
unsigned idx;
for (idx = 0; idx < RTE_DIM(iommu_types); idx++) {
const struct vfio_iommu_type *t = &iommu_types[idx];
@@ -297,7 +298,8 @@ pci_vfio_set_iommu_type(int vfio_container_fd) {
/* check if we have any supported extensions */
static int
-pci_vfio_has_supported_extensions(int vfio_container_fd) {
+pci_vfio_has_supported_extensions(int vfio_container_fd)
+{
int ret;
unsigned idx, n_extensions = 0;
for (idx = 0; idx < RTE_DIM(iommu_types); idx++) {
--
1.9.1
next prev parent reply other threads:[~2016-07-07 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 22:26 [dpdk-dev] [PATCH 1/2] vfio: fix pci_vfio_map_resource Yong Wang
2016-07-07 22:26 ` Yong Wang [this message]
2016-07-14 13:25 ` Thomas Monjalon
2016-07-14 14:50 ` Burakov, Anatoly
2016-07-14 15:34 ` Dan Aloni
2016-07-15 0:15 ` [dpdk-dev] [PATCH v2] " Yong Wang
2016-07-15 13:05 ` Burakov, Anatoly
2016-07-15 15:32 ` Thomas Monjalon
2016-07-15 16:42 ` Thomas Monjalon
2016-07-15 16:56 ` Thomas Monjalon
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=1467930397-39777-2-git-send-email-yongwang@vmware.com \
--to=yongwang@vmware.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).