From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Sekhar Nori <nsekhar@ti.com>, Bartosz Golaszewski <brgl@bgdev.pl>,
Kevin Hilman <khilman@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Lechner <david@lechnology.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v3 0/2] clocksource: davinci-timer: new driver
Date: Tue, 18 Jun 2019 20:03:43 +0200 [thread overview]
Message-ID: <5250ca8e-81bf-6b93-1f00-8121605e9baf@linaro.org> (raw)
In-Reply-To: <67e4688a-09d5-61a3-7406-a91f55045004@linaro.org>
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@baylibre.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@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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-18 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 8:33 [RFC v3 0/2] clocksource: davinci-timer: new driver Bartosz Golaszewski
2019-06-05 8:33 ` [RFC v3 1/2] clocksource: davinci-timer: add support for clockevents Bartosz Golaszewski
2019-06-05 8:33 ` [RFC v3 2/2] clocksource: timer-davinci: add support for clocksource Bartosz Golaszewski
2019-06-14 10:39 ` [RFC v3 0/2] clocksource: davinci-timer: new driver Sekhar Nori
2019-06-14 14:25 ` Daniel Lezcano
2019-06-18 18:03 ` Daniel Lezcano [this message]
2019-06-19 11:53 ` Sekhar Nori
2019-06-24 5:40 ` Daniel Lezcano
2019-06-24 7:21 ` Bartosz Golaszewski
2019-06-24 7:29 ` Sekhar Nori
2019-06-26 15:16 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5250ca8e-81bf-6b93-1f00-8121605e9baf@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).