diff options
| author | hjelmn@cs.unm.edu <hjelmn@cs.unm.edu> | 2014-01-08 23:50:34 +0000 |
|---|---|---|
| committer | Pete Batard <pete@akeo.ie> | 2014-01-08 23:51:01 +0000 |
| commit | 1eff220474f63d7ea7f8f99bef2a3da9da5324eb (patch) | |
| tree | eba538bb278e18c9a8c70fb244f22dd9e971773e /libusb/sync.c | |
| parent | 85e118aca6425108a408c3ce8b55a8d44fcef73c (diff) | |
| download | libusb-1eff220474f63d7ea7f8f99bef2a3da9da5324eb.tar.gz | |
Misc: Revert all references to libusb/libusb.info
Diffstat (limited to 'libusb/sync.c')
| -rw-r--r-- | libusb/sync.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/libusb/sync.c b/libusb/sync.c index 42e486d..d87032d 100644 --- a/libusb/sync.c +++ b/libusb/sync.c @@ -1,5 +1,5 @@ /* - * Synchronous I/O functions for libusbx + * Synchronous I/O functions for libusb * Copyright © 2007-2008 Daniel Drake <dsd@gentoo.org> * * This library is free software; you can redistribute it and/or @@ -28,7 +28,7 @@ /** * @defgroup syncio Synchronous device I/O * - * This page documents libusbx's synchronous (blocking) API for USB device I/O. + * This page documents libusb's synchronous (blocking) API for USB device I/O. * This interface is easy to use but has some limitations. More advanced users * may wish to consider using the \ref asyncio "asynchronous I/O API" instead. */ @@ -222,9 +222,9 @@ static int do_sync_bulk_transfer(struct libusb_device_handle *dev_handle, * Not all of the data may have been written. * * Also check <tt>transferred</tt> when dealing with a timeout error code. - * libusbx may have to split your transfer into a number of chunks to satisfy + * libusb may have to split your transfer into a number of chunks to satisfy * underlying O/S requirements, meaning that the timeout may expire after - * the first few chunks have completed. libusbx is careful not to lose any data + * the first few chunks have completed. libusb is careful not to lose any data * that may have been transferred; do not assume that timeout conditions * indicate a complete lack of I/O. * @@ -270,9 +270,9 @@ int API_EXPORTED libusb_bulk_transfer(struct libusb_device_handle *dev_handle, * writes. Not all of the data may have been written. * * Also check <tt>transferred</tt> when dealing with a timeout error code. - * libusbx may have to split your transfer into a number of chunks to satisfy + * libusb may have to split your transfer into a number of chunks to satisfy * underlying O/S requirements, meaning that the timeout may expire after - * the first few chunks have completed. libusbx is careful not to lose any data + * the first few chunks have completed. libusb is careful not to lose any data * that may have been transferred; do not assume that timeout conditions * indicate a complete lack of I/O. * |