Jim Harris 17afd268df nvme: call correct remove_cb when device is removed ... When a device is removed, we should use the remove_cb that was specified when the device was originally probed and attached, if one was set. Also add a new spdk_nvme_ctrlr_set_remove_cb API. This can be used for cases where a different remove_ctx is desired than was specified for the probe call. This also enables setting a remove_cb when using connect APIs which do not have a way currently to provide a remove_cb. This also requires fixing the bdev nvme module, which was depending on the previously errant behavior. Fixes issue #1715. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id848b39040099ff7a21fe57ea6b194a8c25ae015 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5510 Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: <dongx.yi@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>		2020-12-14 14:34:42 +00:00
..
linux	vhost: update virtion_config.h and virtio_ring.h	2019-12-20 10:04:27 +00:00
spdk	nvme: call correct remove_cb when device is removed	2020-12-14 14:34:42 +00:00
spdk_internal	sock: create spdk_sock_prep_reqs function.	2020-11-27 09:22:30 +00:00
Makefile	build: Copy headers to build/include on build	2020-06-15 15:27:16 +00:00