Richard Zhao <richard.zhao@xxxxxxxxxxxxx> writes: > On Fri, Jun 15, 2012 at 10:46:26AM +0800, Richard Zhao wrote: >> On Thu, Jun 14, 2012 at 08:46:24AM -0700, Greg KH wrote: >> > On Thu, Jun 14, 2012 at 10:52:57AM +0300, Alexander Shishkin wrote: >> > > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: >> > > >> > > > On Fri, Jun 08, 2012 at 08:37:06PM +0800, Richard Zhao wrote: >> > > >> Sometimes, the driver bindings may know what phy they use. >> > > >> For example, when using device tree, the usb controller may have a >> > > >> phandler pointing to usb phy. >> > > >> >> > > >> Signed-off-by: Richard Zhao <richard.zhao@xxxxxxxxxxxxx> >> > > >> Reviewed-by: Marek Vasut <marex@xxxxxxx> >> > > >> Acked-by: Felipe Balbi <balbi@xxxxxx> >> > > >> --- >> > > >> Changes since laster version: >> > > >> - hcd transceiver renamed to phy >> > > > >> > > > Ick, I see patches all over this thread, and other threads, and I have >> > > > no idea what to apply anywhere... >> > > > >> > > > So, consider all chipidea patches dropped from my queue now, can you >> > > > please resend them to me, with the accumulated acks and reviewed-by >> > > > line, so that I can queue them up? >> > > >> > > So will you pick these patches to your tree or should I apply them to >> > > mine or what is the plan? I kind of have a tree [1] for chipidea stuff >> > > where I have been collecting patches, to send a pull request to you for >> > > 3.6. >> > >> > I do not accept pull requests for this code, sorry, I need patches in >> > email. You and Richard work it out how you are going to handle this and >> > then, send me patches that you both agree on. >> So, Alex, Could you send out patch you queued? And I'll send out v6 >> patch series which depends on that. Is it ok for driver part? > All right, I'll send out all. Yes, I think it's easiest if you send everything this time. Please make sure to rebase it on usb-next first, though. Regards, -- Alex -- 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
