On Wed, Nov 23, 2011 at 11:03:31AM +0100, Julian Sikorski wrote: > W dniu 23.11.2011 11:00, Andiry Xu pisze: > > On 11/23/2011 05:39 PM, Julian Sikorski wrote: > >> W dniu 18.11.2011 07:04, Andiry Xu pisze: > >>> On 11/18/2011 07:14 AM, Sarah Sharp wrote: > >>>> Hi Andiry, > >>>> > >>>> Is this necessary for all NEC uPD720200 chipsets, or just the one in > >>>> Julian's board? I have one of those chipsets in my x220 laptop, so I > >>>> can double check if you don't know. > >>>> > >>> > >>> I'm not sure. I have a NEC uPD720200 external controller, but I can't > >>> test the patch because the host fail to resume on my platform and > >>> re-initialize during resume without the quirk. So it would be great if > >>> you can double check. > >>> > >>> Thanks, > >>> Andiry > >>> > >> What is the status of this? I would also like to ask in which timeframe > >> could this patch be merged with? 3.2? 3.3? 3.1.x? > >> > > > > Please be patient, patch merging needs some time, and maintainer has a > > lot of things to take care of:) > > > > Thanks, > > Andiry > > > Sorry about that. I am perfectly fine with applying this patch myself > for a while, I am just curious about the merging process :) Hi Julian, I haven't had time to check whether the NEC uPD720200 chipset in my own x220 laptop is stable after a system resume, which is why I've been holding back on sending this up to Greg KH. If only your system is effected, I'd rather make the patch apply only to that system, because otherwise all NEC uPD720200 will not get persistent storage across system suspend and resume. But in general for xHCI patches, I sign off on them, send them off to the USB subsystem maintainer, Greg KH, and then he sends a batch off to Linus for inclusion in mainline. Greg sends those off roughly every week or every two weeks. The patch should get into the 3.2 kernel, and will probably be marked for inclusion in the stable kernels as well. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
