On Wed, Apr 17, 2013 at 01:44:26PM -0700, Stephen Boyd wrote:
> Thomas,
>
> Would you be able to pick up patches 1 and 2 from this series and
> publish it as a stable branch? Preferably based on rc5 but I can always
> merge it to rc5 and apply the rest of the patches.
>
> Arnd/Olof,
>
> Would
On Wed, Apr 17, 2013 at 01:44:26PM -0700, Stephen Boyd wrote:
Thomas,
Would you be able to pick up patches 1 and 2 from this series and
publish it as a stable branch? Preferably based on rc5 but I can always
merge it to rc5 and apply the rest of the patches.
Arnd/Olof,
Would you be
Thomas,
Would you be able to pick up patches 1 and 2 from this series and
publish it as a stable branch? Preferably based on rc5 but I can always
merge it to rc5 and apply the rest of the patches.
Arnd/Olof,
Would you be able to merge in the rest of the patches to arm-soc? I can
provide a
Thomas,
Would you be able to pick up patches 1 and 2 from this series and
publish it as a stable branch? Preferably based on rc5 but I can always
merge it to rc5 and apply the rest of the patches.
Arnd/Olof,
Would you be able to merge in the rest of the patches to arm-soc? I can
provide a
In light of Mark Rutland's recent work on divorcing the ARM architected
timers from the ARM local timer API and introducing a generic arch hook for
broadcast it seems that we should remove the local timer API entirely.
Doing so will reduce the architecture dependencies of our timer drivers,
reduce
In light of Mark Rutland's recent work on divorcing the ARM architected
timers from the ARM local timer API and introducing a generic arch hook for
broadcast it seems that we should remove the local timer API entirely.
Doing so will reduce the architecture dependencies of our timer drivers,
reduce
6 matches
Mail list logo
