Commit f318a44e authored by Dong Bo's avatar Dong Bo Committed by Jonathan Corbet

vfio: fix documentation

Update vfio_add_group_dev description to match the current API.
Signed-off-by: default avatarDong Bo <dongbo4@huawei.com>
Reviewed-by: default avatarCornelia Huck <cohuck@redhat.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 1897e8f3
...@@ -252,15 +252,14 @@ into VFIO core. When devices are bound and unbound to the driver, ...@@ -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() the driver should call vfio_add_group_dev() and vfio_del_group_dev()
respectively:: respectively::
extern int vfio_add_group_dev(struct iommu_group *iommu_group, extern int vfio_add_group_dev(struct device *dev,
struct device *dev,
const struct vfio_device_ops *ops, const struct vfio_device_ops *ops,
void *device_data); void *device_data);
extern void *vfio_del_group_dev(struct device *dev); extern void *vfio_del_group_dev(struct device *dev);
vfio_add_group_dev() indicates to the core to begin tracking the 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 a VFIO bus driver. The driver provides an ops structure for callbacks
similar to a file operations structure:: similar to a file operations structure::
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment