On Tue, Apr 09, 2013 at 11:39:16AM +0300, Roger Quadros wrote:
> Samuel,
>
> You had the conflicts because a patch [*] was introduced and is not
> required since the reset logic is being removed from the driver.
>
> Anyways, I've rebased the 2 patches on top of mfd-next, so now it
> shouldn't mat
Samuel,
You had the conflicts because a patch [*] was introduced and is not
required since the reset logic is being removed from the driver.
Anyways, I've rebased the 2 patches on top of mfd-next, so now it
shouldn't matter.
cheers,
-roger
[*]
commit 71f4b9cdfccfb82cff702fe61f4ace97a1dfb0e0
Aut
Hi Roger,
On Mon, Mar 25, 2013 at 12:42:04PM +0200, Roger Quadros wrote:
> Hi Samuel,
>
> I've rebased this now on top of 3.9-rc4. Please pull this into your
> next branch when appropriate. Thanks.
>
> The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
>
> Linux 3.9-
Hi Samuel,
I've rebased this now on top of 3.9-rc4. Please pull this into your
next branch when appropriate. Thanks.
The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
Linux 3.9-rc4 (2013-03-23 16:52:44 -0700)
are available in the git repository at:
git://github.co
Hi Samuel,
These patches implement device tree support for the OMAP High Speed
USB Host subsystem. The corresponding EHCI & SoC patches will be sent
separately and this set has no build dependencies with them.
Patch 3 is acutally a bug fix which should go into 3.9-rc. I've sent
it separately to y
