| commit | da87201f7a5580db16565b1ecc7eefe0fcb5bb59 | [log] [tgz] |
|---|---|---|
| author | Chris Dickens <christopher.a.dickens@gmail.com> | Thu Apr 16 16:47:01 2020 -0700 |
| committer | Chris Dickens <christopher.a.dickens@gmail.com> | Thu Apr 23 11:10:31 2020 -0700 |
| tree | a1fee02334808bc4591342f23ab1a16aed3732d9 | |
| parent | be57525e8bb78eb9dcd3efb8ec792e3395b9a140 [diff] |
hotplug: Fix definition of libusb_hotplug_register_callback()
The signature of the libusb_hotplug_register_callback() is slightly
incorrect in two regards:
1) The 'events' parameter is meant to represent a bitwise OR of
libusb_hotplug_event values. By OR'ing multiple values together,
the result is not something that is actually a libusb_hotplug_event
enumeration.
2) The 'flags' parameter is meant to represent a bitwise OR of
libusb_hotplug_flag values. The same considerations as above apply,
though this has not practically been the case as there is currently
only one flag value defined. However, a special value was already
defined to represent the absence of any flags, which hinted at the
problem with how it is currently defined.
Address these two issues by changing the types of the 'events' and
'flags' parameter to plain integers. As enumerations should already be
promoted to integers, this change should not cause any ABI concerns.
Closes #714
Signed-off-by: Chris Dickens <christopher.a.dickens@gmail.com>
libusb is a library for USB device access from Linux, macOS, Windows, OpenBSD/NetBSD, Haiku and Solaris userspace. It is written in C (Haiku backend in C++) and licensed under the GNU Lesser General Public License version 2.1 or, at your option, any later version (see COPYING).
libusb is abstracted internally in such a way that it can hopefully be ported to other operating systems. Please see the PORTING file for more information.
libusb homepage: http://libusb.info/
Developers will wish to consult the API documentation: http://api.libusb.info
Use the mailing list for questions, comments, etc: http://mailing-list.libusb.info
(Please use the mailing list rather than mailing developers directly)