Hi Ravi, On Tue, Nov 19, 2013 at 3:56 PM, Ravi kumar Veeramally <ravikumar.veeramally@xxxxxxxxxxxxxxx> wrote: > This can be tested with haltest. I think this should be already handled by Core service. Were you able to get success response from daemon on multiple sequent init or cleanup calls? btw: I think we should fix this on hal side as well, currently only bluetooth hal is handling error from daemon correctly. There is also question if we should return success on second init call... -- BR Szymon Janc -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
