Hi Szymon, >>> --- >>> android/bluetooth.c | 24 +++++++++++------------- >>> 1 file changed, 11 insertions(+), 13 deletions(-) >>> >>> diff --git a/android/bluetooth.c b/android/bluetooth.c >>> index 8f08122..3314267 100644 >>> --- a/android/bluetooth.c >>> +++ b/android/bluetooth.c >>> @@ -54,6 +54,9 @@ >>> >>> #define DUT_MODE_FILE "/sys/kernel/debug/bluetooth/hci%u/dut_mode" >>> >>> +#define SETTINGS_FILE ANDROID_STORAGEDIR"/settings" >>> +#define DEVICES_FILE ANDROID_STORAGEDIR"/devices” >> >> is there any good reason to keep cached devices together with the bonded >> devices? I get the feeling a cached device should be safe to throw away. So >> deleting the cache file should not cause any problems. Meaning it should be >> a separate file. > > I'm fine with having separate files too (even have this implemented on my > local branch), but wanted to avoid handling multiple files. Anyway, add/remove > bond doesn't happen that often so maybe this is not a problem. > > So, is "device_cache" name OK? Or just "cache”? I would just do “cache” and see where it takes us. Regards Marcel -- 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
