From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Kevin Hilman <khilman@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.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: Fri, 14 Jun 2019 16:09:26 +0530 [thread overview]
Message-ID: <1ac8cfcf-1d77-9b6b-4aab-4171f6cf80fc@ti.com> (raw)
In-Reply-To: <20190605083334.22383-1-brgl@bgdev.pl>
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?
Thanks,
Sekhar
_______________________________________________
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-14 10:43 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 ` Sekhar Nori [this message]
2019-06-14 14:25 ` [RFC v3 0/2] clocksource: davinci-timer: new driver Daniel Lezcano
2019-06-18 18:03 ` Daniel Lezcano
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=1ac8cfcf-1d77-9b6b-4aab-4171f6cf80fc@ti.com \
--to=nsekhar@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=daniel.lezcano@linaro.org \
--cc=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).