On Tue, Sep 18, 2012 at 04:06:49PM +0100, Greg KH wrote: > On Tue, Sep 18, 2012 at 10:42:30AM -0400, Konrad Rzeszutek Wilk wrote: > > On Tue, Sep 18, 2012 at 12:23:02PM +0100, Jan Beulich wrote: > > > Just like for the in-tree early console debug port driver, the > > > hypervisor - when using a debug port based console - also needs to be > > > told about controller resets, so it can suppress using and then > > > re-initialize the debug port accordingly. > > > > > > Other than the in-tree driver, the hypervisor driver actually cares > > > about doing this only for the device where the debug is port actually > > > in use, i.e. it needs to be told the coordinates of the device being > > > reset (quite obviously, leveraging the addition done for that would > > > likely benefit the in-tree driver too). > > > > > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> > > > > Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> > > > > on the *xen* parts. > > So, I'm guessing this should go in through the USB tree? If there are > no objections, I'll do that. No objections. Thank you. -- 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
