Hi Tanu,
On Fri, Nov 15, 2013 at 4:29 PM, Tanu Kaskinen
tanu.kaski...@linux.intel.com wrote:
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
adapter goes missing at a later point, device_info_valid gets set to
-1
On Sun, 2013-11-17 at 18:05 +0200, Luiz Augusto von Dentz wrote:
Hi Tanu,
On Fri, Nov 15, 2013 at 4:29 PM, Tanu Kaskinen
tanu.kaski...@linux.intel.com wrote:
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
adapter goes missing at a later point, device_info_valid gets set to
-1 also in that situation.
---
src/modules/bluetooth/bluez5-util.c | 4 +++-
1 file changed, 3
On Sun, Sep 29, 2013 at 12:49 PM, Tanu Kaskinen
tanu.kaski...@linux.intel.com wrote:
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
adapter goes missing at a later point, device_info_valid gets set to
-1.
---
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
adapter goes missing at a later point, device_info_valid gets set to
-1.
---
src/modules/bluetooth/bluez5-util.c | 4 +++-
1 file changed, 3 insertions(+), 1
