From: Jon Hunter <jonathanh@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sumit Gupta <sumitg@nvidia.com>, <rjw@rjwysocki.net>,
<thierry.reding@gmail.com>, <linux-pm@vger.kernel.org>,
<linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <ksitaraman@nvidia.com>,
<bbasu@nvidia.com>
Subject: Re: [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq
Date: Mon, 5 Oct 2020 10:12:44 +0100 [thread overview]
Message-ID: <207633bf-492b-02e6-b6df-55958ba53d0e@nvidia.com> (raw)
In-Reply-To: <20201005043433.hvyjmzafazg46kvv@vireshk-i7>
On 05/10/2020 05:34, Viresh Kumar wrote:
> On 17-09-20, 09:36, Jon Hunter wrote:
>> Viresh, ideally we need to include this fix for v5.9. Do you need Sumit
>> to resend with the Fixes tag or are you happy to add?
>
> I understand that this fixes a patch which got merged recently, but I am not
> sure if anything is broken badly right now, i.e. will make the hardware work
> incorrectly.
>
> Do we really need to get these in 5.9 ? As these are significant changes and may
> cause more bugs. Won't getting them in 5.9-stable and 5.10-rc1 be enough ?
Yes we want these in v5.9 ideally but yes we could merge to 5.9-stable
once accepted into the mainline.
Jon
--
nvpublic
next prev parent reply other threads:[~2020-10-05 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 17:11 [Patch 0/2] Tegra194 cpufreq driver misc changes Sumit Gupta
2020-09-16 17:11 ` [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq Sumit Gupta
2020-09-17 8:36 ` Jon Hunter
2020-09-17 8:44 ` Jon Hunter
2020-09-23 8:34 ` Jon Hunter
2020-10-05 4:34 ` Viresh Kumar
2020-10-05 9:12 ` Jon Hunter [this message]
2020-09-24 8:56 ` Thierry Reding
2020-10-05 4:46 ` Viresh Kumar
2020-10-05 18:40 ` Sumit Gupta
2020-09-16 17:11 ` [Patch 2/2] cpufreq: tegra194: Fix unlisted boot freq warning Sumit Gupta
2020-09-17 8:38 ` Jon Hunter
2020-09-17 8:45 ` Jon Hunter
2020-09-24 8:56 ` Thierry Reding
2020-10-05 4:54 ` Viresh Kumar
2020-10-05 18:54 ` Sumit Gupta
2020-10-06 5:38 ` Viresh Kumar
2020-10-08 11:11 ` Sumit Gupta
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=207633bf-492b-02e6-b6df-55958ba53d0e@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=ksitaraman@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=rjw@rjwysocki.net \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.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).