diff options
author | 2022-07-28 22:49:13 +0200 | |
---|---|---|
committer | 2022-08-01 13:36:47 -0600 | |
commit | 96a4c9ecaeac2863d53c086d4b5ec9985ba7154f (patch) | |
tree | c011f91463e4aa4fe26b467af8f46c0fa7cc8724 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | vfio/ccw: Add length to DMA_UNMAP checks (diff) | |
download | wireguard-linux-96a4c9ecaeac2863d53c086d4b5ec9985ba7154f.tar.xz wireguard-linux-96a4c9ecaeac2863d53c086d4b5ec9985ba7154f.zip |
vfio/ccw: Remove FSM Close from remove handlers
Now that neither vfio_ccw_sch_probe() nor vfio_ccw_mdev_probe()
affect the FSM state, it doesn't make sense for their _remove()
counterparts try to revert things in this way. Since the FSM open
and close are handled alongside MDEV open/close, these are
unnecessary.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/20220728204914.2420989-3-farman@linux.ibm.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions