Seth Howell 241d04467d example/nvmf: always return after spdk_subsystem_init ... When the call to spdk_subsystem_init returns synchronously, calling the callback results in double iterating over states in the state machine. Returning after calling spdk_subsystem_init allows us to reliably begin executing after the callback function is executed with no double execution. Change-Id: Ieb9003acece7483c956f19be4f131c8d4f64fbaa Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/480007 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com>		2020-01-13 01:47:30 +00:00
..
bdev	bdev/fio: always set the engine_data to NULL	2019-11-06 14:49:00 +00:00
blob	examples/blob: Optional VMD enumeration	2019-07-01 03:53:06 +00:00
ioat	examples: rename ioat perf tool to ioat_perf	2019-05-22 14:51:01 +00:00
nvme	perf: Unify the unit name of IOPS.	2019-12-23 08:43:53 +00:00
nvmf	example/nvmf: always return after spdk_subsystem_init	2020-01-13 01:47:30 +00:00
sock	examples/sock: make hello_sock leverage net subsystem	2019-09-26 15:22:21 +00:00
vmd	examples/vmd/led: LED management app	2019-10-24 17:04:04 +00:00
Makefile	nvmf_example: add an nvmf example	2019-12-20 10:03:34 +00:00