Jim Harris 1cbc41021c thread: return int from spdk_thread_seng_msg ... This at least allows the caller to know there was a problem, and that the messages wasn't actually sent. SPDK by default creates huge rings so this problem should never occur, but out-of-tree use cases may send messages much more often and require at least a notification when it fails. While here, change the thread check to an assert. There's no need to work around someone calling this function with a null thread parameter. Fixes issue #811. Signed-off-by: Jim Harris <james.r.harris@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/472438 (master) (cherry picked from commit 4036f95bf8) Change-Id: Ie6d432d616be45c7a4232aff1548cef198702bc0 Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478442 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>		2019-12-23 08:04:56 +00:00
..
linux	vhost-blk: add discard/write zeroes commands support	2019-01-12 03:14:48 +00:00
spdk	thread: return int from spdk_thread_seng_msg	2019-12-23 08:04:56 +00:00
spdk_internal	sock/posix: Store pointer to group in sock	2019-10-15 16:35:09 +00:00
Makefile	Makefile: Add possibility to uninstall spdk.	2019-05-16 20:56:18 +00:00