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 /samples | |
| parent | f4da83f7e3f096ece936512d86ef3726e470fbfd (diff) | |
| download | linux-d1104f9327df9b26901b97cd026949f80ccab0d3.tar.bz2 | |
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 'samples')
0 files changed, 0 insertions, 0 deletions