From 728af01741502d1da141b1e0c4d2d6745cf1a46e Mon Sep 17 00:00:00 2001 From: Darek Stojaczyk Date: Wed, 3 Apr 2019 17:18:08 +0200 Subject: [PATCH] event/nvmf: allow running without [Transport] in the legacy cfg file While useful in NVMf target, this is really annoying in the consolidated spdk target, where NVMe-oF doesn't even have to be used. OCF tests currently use iscsi_tgt just because spdk_tgt requires the additional [Transport] section in the cfg file. Let's remove that requirement. Change-Id: I418b47d62dcc06b9513f9f0496dc1e39b9d5a554 Signed-off-by: Darek Stojaczyk Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/450056 Reviewed-by: Vitaliy Mysak Reviewed-by: Ben Walker Reviewed-by: Shuhei Matsumoto Reviewed-by: Jim Harris Tested-by: SPDK CI Jenkins --- lib/event/subsystems/nvmf/conf.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/lib/event/subsystems/nvmf/conf.c b/lib/event/subsystems/nvmf/conf.c index 6d29247e7..8f342e8aa 100644 --- a/lib/event/subsystems/nvmf/conf.c +++ b/lib/event/subsystems/nvmf/conf.c @@ -581,11 +581,7 @@ spdk_nvmf_parse_transports(spdk_nvmf_parse_conf_done_fn cb_fn) /* if we get here, there are no transports defined in conf file */ free(ctx); - SPDK_ERRLOG("\nNo valid transport is defined yet.\n" - "When using configuration file, at least one valid transport must be defined.\n" - "You can refer the [Transport] section in spdk/etc/spdk/nvmf.conf.in as an example.\n"); - cb_fn(-1); - + cb_fn(0); return 0; }