Fix docs about backend functions that lock itransfer->lock
In 2013, commit 858b794c added a comment saying "This function gets
called with the flying_transfers_lock locked".
That appears to have changed with 138b661f. Commit 88778414 improved
some stale comments, but missed these.
It is clear in the code that the comment is no longer true. The function
is *not* called with flying_transfers_lock locked, but it does lock
itransfer->lock.
References #1410
diff --git a/libusb/libusbi.h b/libusb/libusbi.h
index eaa02ad..c6e032d 100644
--- a/libusb/libusbi.h
+++ b/libusb/libusbi.h
@@ -1351,7 +1351,7 @@
*
* This function must not block.
*
- * This function gets called with the flying_transfers_lock locked!
+ * This function gets called with itransfer->lock locked!
*
* Return:
* - 0 on success
@@ -1365,6 +1365,8 @@
* This function must not block. The transfer cancellation must complete
* later, resulting in a call to usbi_handle_transfer_cancellation()
* from the context of handle_events.
+ *
+ * This function gets called with itransfer->lock locked!
*/
int (*cancel_transfer)(struct usbi_transfer *itransfer);
diff --git a/libusb/version_nano.h b/libusb/version_nano.h
index 762be6b..208969c 100644
--- a/libusb/version_nano.h
+++ b/libusb/version_nano.h
@@ -1 +1 @@
-#define LIBUSB_NANO 11866
+#define LIBUSB_NANO 11867
