[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <36f5940b-cac5-9a4a-86cb-7ad9766d5d62@huawei.com>
Date: Fri, 20 Apr 2018 18:07:27 +0800
From: "dongbo (E)" <dongbo4@...wei.com>
To: <alex.williamson@...hat.com>, <corbet@....net>
CC: <kvm@...r.kernel.org>, <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [PATCH] VFIO: Fix Documentation
From: Dong Bo <dongbo4@...wei.com>
Signed-off-by: Dong Bo <dongbo4@...wei.com>
---
Documentation/vfio.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
index ef6a511..f1a4d3c 100644
--- a/Documentation/vfio.txt
+++ b/Documentation/vfio.txt
@@ -252,15 +252,14 @@ into VFIO core. When devices are bound and unbound to the driver,
the driver should call vfio_add_group_dev() and vfio_del_group_dev()
respectively::
- extern int vfio_add_group_dev(struct iommu_group *iommu_group,
- struct device *dev,
+ extern int vfio_add_group_dev(struct device *dev,
const struct vfio_device_ops *ops,
void *device_data);
extern void *vfio_del_group_dev(struct device *dev);
vfio_add_group_dev() indicates to the core to begin tracking the
-specified iommu_group and register the specified dev as owned by
+iommu_group of the specified dev and register the dev as owned by
a VFIO bus driver. The driver provides an ops structure for callbacks
similar to a file operations structure::
-- 1.9.1
.
Powered by blists - more mailing lists