[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <22da4309-a1a5-c2a3-df83-57398d824fe7@linaro.org>
Date: Wed, 26 Jun 2019 17:16:42 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Sekhar Nori <nsekhar@...com>, Bartosz Golaszewski <brgl@...ev.pl>
Cc: Kevin Hilman <khilman@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
David Lechner <david@...hnology.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [RFC v3 0/2] clocksource: davinci-timer: new driver
On 24/06/2019 09:29, Sekhar Nori wrote:
> On 24/06/19 12:51 PM, Bartosz Golaszewski wrote:
>> pon., 24 cze 2019 o 07:40 Daniel Lezcano <daniel.lezcano@...aro.org> napisał(a):
>>>
>>>
>>> Sekhar, Bartosz,
>>>
>>> if the sparse warning is not fixed, the driver won't hit this kernel
>>> version. Please fix it before the two next days otherwise it won't make
>>> it for v5.4.
>>>
>>> Thanks
>>>
>>
>> Hi Daniel,
>>
>> will do, I just came back to the office.
>>
>> Sekhar, how do we want to handle the rest of the platform code with
>> this driver? Do you think it can make it for the next release?
>
> It may have to wait till next release, I am afraid. Lets first try to
> get the driver in though. I can try a late pull request with no guarantees.
The driver is merged in tip/timers/core, however I messed up with the
davinci branch, please do not consider it as an immutable branch.
Sorry for that.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
Powered by blists - more mailing lists