From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Jon Hunter <jonathanh@nvidia.com>,
Kartik Kartik <kkartik@nvidia.com>,
linux-rtc@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] rtc: tegra: Dust off and deferred probe support
Date: Sat, 1 Jun 2019 22:39:55 +0200 [thread overview]
Message-ID: <20190601203955.GZ3274@piout.net> (raw)
In-Reply-To: <20190527101359.5898-1-thierry.reding@gmail.com>
On 27/05/2019 12:13:56+0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The NVIDIA Tegra RTC driver has accumulated a bit of dust over the
> years. Make a pass over it, addressing checkpatch warnings and fixing
> some inconsistencies in comments and kernel messages as well as in
> variable types and names.
>
> Once cleaned up, also turn the driver into a regular driver in order
> to support deferred probe which is needed to avoid a future regression
> on Tegra186 and later.
>
> Thierry
>
> Thierry Reding (3):
> rtc: tegra: checkpatch and miscellaneous cleanups
> rtc: tegra: Use consistent variable names and types
> rtc: tegra: Turn into regular driver
>
> drivers/rtc/rtc-tegra.c | 254 ++++++++++++++++++++--------------------
> 1 file changed, 128 insertions(+), 126 deletions(-)
>
All applied, thanks.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-01 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 10:13 [PATCH 0/3] rtc: tegra: Dust off and deferred probe support Thierry Reding
2019-05-27 10:13 ` [PATCH 1/3] rtc: tegra: checkpatch and miscellaneous cleanups Thierry Reding
2019-05-27 11:28 ` Dmitry Osipenko
2019-05-27 10:13 ` [PATCH 2/3] rtc: tegra: Use consistent variable names and types Thierry Reding
2019-05-27 10:13 ` [PATCH 3/3] rtc: tegra: Turn into regular driver Thierry Reding
2019-06-01 20:39 ` Alexandre Belloni [this message]
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=20190601203955.GZ3274@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).