[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3734641.73qX0VsHyn@kreacher>
Date: Mon, 27 May 2019 12:51:32 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: linux-kernel@...r.kernel.org, Markus Mayer <mmayer@...adcom.com>,
"maintainer:BROADCOM STB AVS CPUFREQ DRIVER"
<bcm-kernel-feedback-list@...adcom.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Brian Norris <computersforpeace@...il.com>,
Gregory Fong <gregory.0xf0@...il.com>,
"open list:BROADCOM STB AVS CPUFREQ DRIVER"
<linux-pm@...r.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes
On Wednesday, May 22, 2019 8:45:45 PM CEST Florian Fainelli wrote:
> Hi Rafael, Viresh,
>
> These patch series contains two minor fixes for the brcmstb-avs-cpufreq
> driver.
>
> Florian Fainelli (2):
> cpufreq: brcmstb-avs-cpufreq: Fix initial command check
> cpufreq: brcmstb-avs-cpufreq: Fix types for voltage/frequency
>
> drivers/cpufreq/brcmstb-avs-cpufreq.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
These look straightforward enough to me, but it would be good to get an ACK from the
driver maintainer for them.
Powered by blists - more mailing lists