On Thu, Sep 27, 2012 at 3:49 AM, Greg KH <[email protected]> wrote: > On Mon, Aug 20, 2012 at 02:57:58PM +0530, Keshava Munegowda wrote: >> This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled >> "Fix OMAP EHCI suspend/resume failure (i693)" is causing >> the usb hub and device detection fails in beagle XM >> causeing NFS not functional. This affects the core retention too. >> The same commit logic needs to be revisted adhering to hwmod and >> device tree framework. >> for now, this commit id 354ab8567ae3107a8cbe7228c3181990ba598aac >> titled "Fix OMAP EHCI suspend/resume failure (i693)" reverted. >> >> This patch is validated on BeagleXM with NFS support over >> usb ethernet and USB mass storage and other device detection. >> >> V2: >> rebased to linux kernel "stable" version 3.5.2 release >> not applicable to mainline linux release >> >> Signed-off-by: Keshava Munegowda <[email protected]> >> Acked-by: Felipe Balbi <[email protected]> >> Signed-off-by: Greg Kroah-Hartman <[email protected]> >> --- >> drivers/usb/host/ehci-omap.c | 164 >> +----------------------------------------- > > Ok, why isn't this an issue in 3.6-rc7? Did it get fixed differently > there? If so, what is that git commit id? If not, why not? > > confused, > > greg k-h
This patch was not existing only in stable release 3.5.2 and it was not applying too. I had received a mail from you ( aug 17) to fix the same . hence this v2. it is already available in 3.6-rc7 and the commit id is 872c495dd0f9d1f48814a8ee80c2c7b3b7c3b4d9 please do let me know if you are facing any problem with this patch ; so that i can fix it immediately. regards keshava ------- piece of your mail :-) -------------------------------- "The patch below does not apply to the 3.5-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>." thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
