diff options
| author |   Eric Farman <farman@linux.ibm.com> | 2022-11-04 15:20:06 +0100 |
|---|---|---|
| committer |   Alex Williamson <alex.williamson@redhat.com> | 2022-11-10 11:30:23 -0700 |
| commit | d1104f9327df9b26901b97cd026949f80ccab0d3 (patch) | |
| tree | 42819b4942ab4a01a5f1345bf19c76035242fcb9 /include/linux/vfio.h | |
| parent | vfio/ccw: remove release completion (diff) | |
| download | wireguard-linux-d1104f9327df9b26901b97cd026949f80ccab0d3.tar.xz wireguard-linux-d1104f9327df9b26901b97cd026949f80ccab0d3.zip | |
vfio/ccw: replace vfio_init_device with _alloc_
Now that we have a reasonable separation of structs that follow
the subchannel and mdev lifecycles, there's no reason we can't
call the official vfio_alloc_device routine for our private data,
and behave like everyone else.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Link: https://lore.kernel.org/r/20221104142007.1314999-7-farman@linux.ibm.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'include/linux/vfio.h')
| -rw-r--r-- | include/linux/vfio.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/include/linux/vfio.h b/include/linux/vfio.h index e7cebeb875dd..ba809268a48e 100644 --- a/include/linux/vfio.h +++ b/include/linux/vfio.h @@ -176,8 +176,6 @@ struct vfio_device *_vfio_alloc_device(size_t size, struct device *dev, dev, ops), \ struct dev_struct, member) -int vfio_init_device(struct vfio_device *device, struct device *dev, - const struct vfio_device_ops *ops); void vfio_free_device(struct vfio_device *device); static inline void vfio_put_device(struct vfio_device *device) { |