Signed-off-by: Márton Németh <[email protected]>
---
--- linux-2.6.30-rc7/Documentation/usb/callbacks.txt.orig 2009-03-24 00:12:14.000000000 +0100
+++ linux-2.6.30-rc7/Documentation/usb/callbacks.txt 2009-06-03 19:51:07.000000000 +0200
@@ -65,7 +65,7 @@ Accept or decline an interface. If you a
otherwise -ENODEV or -ENXIO. Other error codes should be used only if a
genuine error occurred during initialisation which prevented a driver
from accepting a device that would else have been accepted.
-You are strongly encouraged to use usbcore'sfacility,
+You are strongly encouraged to use usbcore's facility,
usb_set_intfdata(), to associate a data structure with an interface, so
that you know which internal state and identity you associate with a
particular interface. The device will not be suspended and you may do IO
On Sat, 6 Jun 2009, Németh Márton wrote:
> Signed-off-by: Márton Németh <[email protected]>
> ---
> --- linux-2.6.30-rc7/Documentation/usb/callbacks.txt.orig 2009-03-24 00:12:14.000000000 +0100
> +++ linux-2.6.30-rc7/Documentation/usb/callbacks.txt 2009-06-03 19:51:07.000000000 +0200
> @@ -65,7 +65,7 @@ Accept or decline an interface. If you a
> otherwise -ENODEV or -ENXIO. Other error codes should be used only if a
> genuine error occurred during initialisation which prevented a driver
> from accepting a device that would else have been accepted.
> -You are strongly encouraged to use usbcore'sfacility,
> +You are strongly encouraged to use usbcore's facility,
> usb_set_intfdata(), to associate a data structure with an interface, so
> that you know which internal state and identity you associate with a
> particular interface. The device will not be suspended and you may do IO
Applied to trivial tree, thanks.
--
Jiri Kosina
SUSE Labs