[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231020080339.GA6197@varda-linux.qualcomm.com>
Date: Fri, 20 Oct 2023 13:33:39 +0530
From: Varadarajan Narayanan <quic_varada@...cinc.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: <agross@...nel.org>, <andersson@...nel.org>,
<konrad.dybcio@...aro.org>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<mturquette@...libre.com>, <sboyd@...nel.org>, <rafael@...nel.org>,
<ilia.lin@...nel.org>, <sivaprak@...eaurora.org>,
<quic_kathirav@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-clk@...r.kernel.org>, <linux-pm@...r.kernel.org>
Subject: Re: [PATCH v5 0/9] Enable cpufreq for IPQ5332 & IPQ9574
On Fri, Oct 20, 2023 at 12:39:47PM +0530, Viresh Kumar wrote:
> On 20-10-23, 11:49, Varadarajan Narayanan wrote:
> > Varadarajan Narayanan (9):
> > cpufreq: qti: Enable cpufreq for ipq53xx
> > cpufreq: qti: Introduce cpufreq for ipq95xx
>
> Can I pick just these two ?
ipq53xx patch is dependent on the previous safe source switching
patch, hence not safe to pick that.
No -> cpufreq: qti: Enable cpufreq for ipq53xx
Yes -> cpufreq: qti: Introduce cpufreq for ipq95xx
Thanks
Varada
Powered by blists - more mailing lists