From f4c2074ba8498028df90e9ec346d79b203a42470 Mon Sep 17 00:00:00 2001 From: Masanari Iida Date: Wed, 15 Feb 2012 23:59:47 +0900 Subject: [PATCH] --- yaml --- r: 291742 b: refs/heads/master c: 45f3122622e92fda1ee590ba740fa7cbd82d6ee3 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/usb/power-management.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 52aec0ea442a..702f5e526ba4 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 0c2daf810004e8fe13f8bd40ca8f277aeedbd08d +refs/heads/master: 45f3122622e92fda1ee590ba740fa7cbd82d6ee3 diff --git a/trunk/Documentation/usb/power-management.txt b/trunk/Documentation/usb/power-management.txt index 12511c98cc4f..817df299ea07 100644 --- a/trunk/Documentation/usb/power-management.txt +++ b/trunk/Documentation/usb/power-management.txt @@ -345,7 +345,7 @@ autosuspend the device. Drivers need not be concerned about balancing changes to the usage counter; the USB core will undo any remaining "get"s when a driver is unbound from its interface. As a corollary, drivers must not call -any of the usb_autopm_* functions after their diconnect() routine has +any of the usb_autopm_* functions after their disconnect() routine has returned. Drivers using the async routines are responsible for their own