There are two definitions of resume_device. A global one is defined
in resume.c, and a local one is defined in USB core. The linker appears
to do the right thing, but it is bad practice and makes backtrace
decoding harder.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
--- a/drivers/usb/core/driver.c 2006-11-13 15:05:52.000000000 -0800
+++b/drivers/usb/core/driver.c 2006-11-13 15:06:38.000000000 -0800
@@ -817,7 +817,7 @@
}
/* Caller has locked udev's pm_mutex */
-static int resume_device(struct usb_device *udev)
+static int usb_resume_device(struct usb_device *udev)
{
struct usb_device_driver *udriver;
int status = 0;
@@ -1077,14 +1077,14 @@
status = -EHOSTUNREACH;
}
if (status == 0)
- status = resume_device(udev);
+ status = usb_resume_device(udev);
if (parent)
usb_pm_unlock(parent);
} else {
/* Needed only for setting udev->dev.power.power_state.event
* and for possible debugging message. */
- status = resume_device(udev);
+ status = usb_resume_device(udev);
}
/* Now the parent won't suspend until we are finished */
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
