On Monday 13 January 2014 08:14 AM, Daniel Lezcano wrote: > On 01/13/2014 12:28 PM, ivan.khoronzhuk wrote: >> On 12/28/2013 09:07 PM, Daniel Lezcano wrote: >>> On 12/26/2013 07:02 PM, Santosh Shilimkar wrote: >>>> $subject >>>> s/arm/ARM, >>>> >>>> On Wednesday 25 December 2013 07:32 AM, Ivan Khoronzhuk wrote: >>>>> Add keystone timer entry to keystone device tree. >>>>> This 64-bit timer is used as backup clock event device. >>>>> >>>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@xxxxxx> >>>>> --- >>>> No need to repost. I will fix it up while applying based >>>> on state of PATCH 1/3 and 2/3. >>> >>> I assume you will take the patchset in your tree. >>> >>> I am back from vacations, give me a couple of days to review the >>> patchset before applying it please. >>> >>> Thanks >>> -- Daniel >>> >> >> Hi, Daniel >> >> Do you have any comments on this patch series? >> Can we expect it in k3.14 > > I have applied the patch 1/3 and 2/3 in my tree but I was expecting the DT folks to give their acked-by for the patch 2/3. > > It is a bit late for 3.14 but if the patch 3/3 is in Santosh's tree, the patch 2/3 gets its acked-by and you absolutely need the driver for this version, I may consider to send another PR to the upstream maintainers. That will be up to them to accept to pull it or not. > They can wait for next merge window (3.15). Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
