From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Markus Mayer <code@mmayer.net>,
Markus Mayer <mmayer@broadcom.com>
Cc: linux-kernel@vger.kernel.org,
"maintainer:BROADCOM STB AVS CPUFREQ DRIVER"
<bcm-kernel-feedback-list@broadcom.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
"open list:BROADCOM STB AVS CPUFREQ DRIVER"
<linux-pm@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes
Date: Wed, 29 May 2019 10:01:57 -0700 [thread overview]
Message-ID: <013ec7c0-0984-cfc9-ea3a-0180719f5ac4@gmail.com> (raw)
In-Reply-To: <3734641.73qX0VsHyn@kreacher>
On 5/27/19 3:51 AM, Rafael J. Wysocki wrote:
> 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.
Adding Markus' other email address.
>
>
>
--
Florian
next prev parent reply other threads:[~2019-05-29 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 18:45 [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes Florian Fainelli
2019-05-22 18:45 ` [PATCH 1/2] cpufreq: brcmstb-avs-cpufreq: Fix initial command check Florian Fainelli
2019-05-22 18:45 ` [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: Fix types for voltage/frequency Florian Fainelli
2019-05-27 10:51 ` [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes Rafael J. Wysocki
2019-05-29 17:01 ` Florian Fainelli [this message]
2019-06-03 19:55 ` Markus Mayer
2019-06-04 4:03 ` Viresh Kumar
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=013ec7c0-0984-cfc9-ea3a-0180719f5ac4@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=code@mmayer.net \
--cc=computersforpeace@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=rjw@rjwysocki.net \
--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).