[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5250ca8e-81bf-6b93-1f00-8121605e9baf@linaro.org>
Date: Tue, 18 Jun 2019 20:03:43 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Sekhar Nori <nsekhar@...com>, Bartosz Golaszewski <brgl@...ev.pl>,
Kevin Hilman <khilman@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
David Lechner <david@...hnology.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [RFC v3 0/2] clocksource: davinci-timer: new driver
On 14/06/2019 16:25, Daniel Lezcano wrote:
> On 14/06/2019 12:39, Sekhar Nori wrote:
>> Hi Daniel,
>>
>> On 05/06/19 2:03 PM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski <bgolaszewski@...libre.com>
>>>
>>> This is another version of the new davinci clocksource driver. After much
>>> discussion this contains many changes to simplify and improve the driver.
>>
>> Does this look good to you now? If yes, can you please merge and provide
>> an immutable branch to me so I can merge dependent mach-davinci patches?
>
> Yes, I think it is fine.
>
> http://git@....linaro.org/people/daniel.lezcano/linux.git
> timers/drivers/davinci
>
> It is v5.2-rc4 + (2 x patches)
>
> It is merged in clockevents/next which is exported to linux-next and for
> kernel-ci.
>
> AFAIU, the patch was compiled and tested. If not, please let me know.
>
> Please, wait a couple of days I confirm the tests passed and you can
> consider the branch immutable.
lkp complained, please do not use the branch.
I'm waiting for Bartosz to fix the issue.
--
<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