lightnvm: use end_io callback instead of instance
When the lightnvm core had the "gennvm" layer between the device and the target, there was a need for the core to be able to figure out which target it should send an end_io callback to. Leading to a "double" end_io, first for the media manager instance, and then for the target instance. Now that core and gennvm is merged, there is no longer a need for this, and a single end_io callback will do. Signed-off-by:Matias Bjørling <matias@cnexlabs.com> Signed-off-by:
Jens Axboe <axboe@fb.com>
Showing
- drivers/block/null_blk.c 2 additions, 1 deletiondrivers/block/null_blk.c
- drivers/lightnvm/core.c 3 additions, 4 deletionsdrivers/lightnvm/core.c
- drivers/lightnvm/rrpc.c 3 additions, 4 deletionsdrivers/lightnvm/rrpc.c
- drivers/lightnvm/rrpc.h 0 additions, 3 deletionsdrivers/lightnvm/rrpc.h
- drivers/nvme/host/lightnvm.c 2 additions, 1 deletiondrivers/nvme/host/lightnvm.c
- include/linux/lightnvm.h 3 additions, 7 deletionsinclude/linux/lightnvm.h
Please register or sign in to comment