From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: David Lechner <david@lechnology.com>,
Kevin Hilman <khilman@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v3 0/2] clocksource: davinci-timer: new driver
Date: Mon, 24 Jun 2019 09:21:08 +0200 [thread overview]
Message-ID: <CAMRc=MecrpzwC0-8x=1dAipf+j7h+C54pHCfbZidFGXtAyv7Pg@mail.gmail.com> (raw)
In-Reply-To: <1a66e067-631c-c7a4-288b-3934737bee8c@linaro.org>
pon., 24 cze 2019 o 07:40 Daniel Lezcano <daniel.lezcano@linaro.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?
Bart
_______________________________________________
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-24 7:21 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
2019-06-19 11:53 ` Sekhar Nori
2019-06-24 5:40 ` Daniel Lezcano
2019-06-24 7:21 ` Bartosz Golaszewski [this message]
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='CAMRc=MecrpzwC0-8x=1dAipf+j7h+C54pHCfbZidFGXtAyv7Pg@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--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=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).