From: Dmitry Osipenko <digetx@gmail.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Peter De Schrijver" <pdeschrijver@nvidia.com>,
"Prashant Gaikwad" <pgaikwad@nvidia.com>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 0/7] Couple improvements for Tegra clk driver
Date: Tue, 30 Mar 2021 18:40:14 +0300 [thread overview]
Message-ID: <c4394764-184c-3680-5e6f-2df8d2d18972@gmail.com> (raw)
In-Reply-To: <20210320152648.8389-1-digetx@gmail.com>
20.03.2021 18:26, Dmitry Osipenko пишет:
> This series fixes couple minor standalone problems of the Tegra clk
> driver.
Hello Stephen,
Do you have any objects if Thierry will take this series into the Tegra
tree?
Or will you be able to take the patches into the clk tree?
Please let us know what works best for you, thanks in advance.
prev parent reply other threads:[~2021-03-30 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 15:26 [PATCH v6 0/7] Couple improvements for Tegra clk driver Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 1/7] clk: tegra30: Use 300MHz for video decoder by default Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 2/7] clk: tegra: Fix refcounting of gate clocks Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 3/7] clk: tegra: Ensure that PLLU configuration is applied properly Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 4/7] clk: tegra: Halve SCLK rate on Tegra20 Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 5/7] MAINTAINERS: Hand Tegra clk driver to Jon and Thierry Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 6/7] clk: tegra: Don't allow zero clock rate for PLLs Dmitry Osipenko
2021-03-20 15:26 ` [PATCH v6 7/7] dt-bindings: clock: tegra: Convert to schema Dmitry Osipenko
2021-03-23 22:38 ` Rob Herring
2021-03-30 15:40 ` Dmitry Osipenko [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=c4394764-184c-3680-5e6f-2df8d2d18972@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).