From 5e89d81d9d6b8b1101b1482620b3f85968eb3b47 Mon Sep 17 00:00:00 2001 From: Linus Torvalds Date: Fri, 13 Mar 2020 12:57:15 -0700 Subject: iostream: fix incorrect rfcomm error case when writing This is the exact same case as the previous commit, just for the writing side. Once again, it's the subsurface rfcomm iostream code that can return DC_STATUS_SUCCESS with a byte count of zero when something goes wrong with the write. And once again, our libdivecomputer iostream code didn't try to be robust and protect itself from that case. The fix is equivalent, although slightly simpler, since the write side doesn't have the whole timeout issue. Signed-off-by: Linus Torvalds --- libdivecomputer | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libdivecomputer') diff --git a/libdivecomputer b/libdivecomputer index b77e7b6b2..7882ba423 160000 --- a/libdivecomputer +++ b/libdivecomputer @@ -1 +1 @@ -Subproject commit b77e7b6b217860e166081f8a93fb8bac81797897 +Subproject commit 7882ba423cd87569f9c9361fa999917e9ced1083 -- cgit v1.2.3-70-g09d2