Re: [Libusbx-devel] [PATCH] Don't log an error message when cancel fails due to -ENODEV

2012-09-12 Thread Pete Batard
This patch and the doc/stderr update patch have now been pushed to mainline. I'm planning to add the fxload sample tomorrow, after a bit more testing on my end, and probably the controversial MaxPower -> bMaxPower one too, and then declare RC either tomorrow or Friday. I have also moved the pla

Re: [Libusbx-devel] [PATCH] Don't log an error message when cancel fails due to -ENODEV

2012-09-11 Thread Pete Batard
On 2012.09.11 13:04, Hans de Goede wrote: This patch therefor makes libusb_cancel_transfer not log an error when the cancel fails with LIBUSB_ERROR_NO_DEVICE, so that apps can properly clean things up on device disconnect without flooding the console with these errors. Actually, I'm going to ad

[Libusbx-devel] [PATCH] Don't log an error message when cancel fails due to -ENODEV

2012-09-11 Thread Hans de Goede
A properly written app will cancel any outstanding transfers, before calling libusb_close(), and when an app does not, we complain loudly about it. But currently if a device gets unplugged while transfers are outstanding, and the app detects this disconnect by getting a LIBUSB_ERROR_NO_DEVICE, the