From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
rjw@rjwysocki.net, catalin.marinas@arm.com, will@kernel.org,
thierry.reding@gmail.com, robh+dt@kernel.org,
mirq-linux@rere.qmqm.pl, devicetree@vger.kernel.org,
talho@nvidia.com, linux-pm@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bbasu@nvidia.com,
mperttunen@nvidia.com
Subject: Re: [TEGRA194_CPUFREQ PATCH v6 3/3] cpufreq: Add Tegra194 cpufreq driver
Date: Thu, 16 Jul 2020 09:05:23 +0530 [thread overview]
Message-ID: <20200716033523.fhlfh5m5magifspx@vireshk-i7> (raw)
In-Reply-To: <78636522-c433-a015-e4f3-02843ce58139@nvidia.com>
On 15-07-20, 20:57, Sumit Gupta wrote:
> Sorry, missed to remove this. Will wait if any other comments before
> re-spin.
I don't have any further comments, maybe just send a new version of
this patch alone and name it v6.1.
--
viresh
next prev parent reply other threads:[~2020-07-16 3:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 13:31 [TEGRA194_CPUFREQ PATCH v6 0/3] Add cpufreq driver for Tegra194 Sumit Gupta
2020-07-15 13:31 ` [TEGRA194_CPUFREQ PATCH v6 1/3] dt-bindings: arm: Add NVIDIA Tegra194 CPU Complex binding Sumit Gupta
2020-07-16 16:11 ` Rob Herring
2020-07-15 13:31 ` [TEGRA194_CPUFREQ PATCH v6 2/3] arm64: tegra: Add t194 ccplex compatible and bpmp property Sumit Gupta
2020-07-16 12:37 ` Thierry Reding
2020-07-18 8:29 ` Viresh Kumar
2020-07-15 13:31 ` [TEGRA194_CPUFREQ PATCH v6 3/3] cpufreq: Add Tegra194 cpufreq driver Sumit Gupta
2020-07-15 14:44 ` Jon Hunter
2020-07-15 15:27 ` Sumit Gupta
2020-07-16 3:35 ` Viresh Kumar [this message]
2020-07-16 8:30 ` [TEGRA194_CPUFREQ PATCH v6.1 " Sumit Gupta
2020-08-09 0:40 ` [TEGRA194_CPUFREQ PATCH v6 " Guenter Roeck
2020-08-09 10:11 ` Catalin Marinas
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=20200716033523.fhlfh5m5magifspx@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bbasu@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mperttunen@nvidia.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sumitg@nvidia.com \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=will@kernel.org \
/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).