[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5046772F.6060908@wwwdotorg.org>
Date: Tue, 04 Sep 2012 15:48:31 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: balbi@...com
CC: Venu Byravarasu <vbyravarasu@...dia.com>, ccross@...roid.com,
olof@...om.net, linux@....linux.org.uk, stern@...land.harvard.edu,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH v2] usb: move phy driver from mach-tegra to drivers/usb
On 08/31/2012 12:45 AM, Venu Byravarasu wrote:
> As part of this patch:
> 1. Moved existing tegra phy driver to drivers/USB directory.
> 2. Added standard USB phy driver APIs to tegra phy driver.
>
> Signed-off-by: Venu Byravarasu <vbyravarasu@...dia.com>
Tested-by: Stephen Warren <swarren@...dia.com>
Felipe, Would it be possible to apply this patch to a topic branch, so
that I can merge it into the Tegra tree? The reason is that I'd like to
remove Tegra's devices.[ch] in kernel 3.7, but to do that, I need to
move a tiny chunk of code out of that file somewhere else, and doing
that relies on adding a #include to usb_phy.h/tegra_usb_phy.h, which is
renamed in this patch.
Alternatively, if you don't think it'll cause any merge conflicts with
the USB PHY tree, I can just take this patch through the Tegra tree if
you want. Venu, do you plan any other patches within the next couple
weeks or so (i.e. before 3.6-rc6) that will depend on this patch? If so,
taking it only through the Tegra tree might not work so well.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists