Seth Howell 190b2245c5 test: make xtrace_disable multi-call safe. ... Previously, if you made two sequential calls to xtrace_disable without calling xtrace_enable, you would lose the original value of x. Now this is not the case. It allows us to call xtrace_disable freely without worrying about whether xtrace_disable is invoked later in a function we call. Change-Id: I9818ae97532e7a31db576bb9bd2e2e30d67ab410 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/477965 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>		2019-12-17 14:54:40 +00:00
..
config	Change fio version	2019-12-06 14:50:59 +00:00
lib	sock: Add an asynchronous writev	2019-12-16 12:34:02 +00:00
autotest_common.sh	test: make xtrace_disable multi-call safe.	2019-12-17 14:54:40 +00:00