summaryrefslogtreecommitdiffstats
path: root/Documentation/vfio.txt
diff options
context:
space:
mode:
authorDong Bo <dongbo4@huawei.com>2018-05-07 05:02:10 +0200
committerJonathan Corbet <corbet@lwn.net>2018-05-08 17:16:41 +0200
commitf318a44e15c16307b3f95751b674cb5d63789eb6 (patch)
tree9171ed1fc92e34141059d0fd6c69c736846c42b9 /Documentation/vfio.txt
parentdoc: botching-up-ioctls: Make it clearer why structs must be padded (diff)
downloadlinux-f318a44e15c16307b3f95751b674cb5d63789eb6.tar.xz
linux-f318a44e15c16307b3f95751b674cb5d63789eb6.zip
vfio: fix documentation
Update vfio_add_group_dev description to match the current API. Signed-off-by: Dong Bo <dongbo4@huawei.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/vfio.txt')
-rw-r--r--Documentation/vfio.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
index ef6a5111eaa1..f1a4d3c3ba0b 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::