All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, Markus Mayer <mmayer@broadcom.com>,
	"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: Mon, 27 May 2019 12:51:32 +0200	[thread overview]
Message-ID: <3734641.73qX0VsHyn@kreacher> (raw)
In-Reply-To: <20190522184547.31791-1-f.fainelli@gmail.com>

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.




WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Gregory Fong <gregory.0xf0@gmail.com>,
	"open list:BROADCOM STB AVS CPUFREQ DRIVER"
	<linux-pm@vger.kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-kernel@vger.kernel.org,
	"maintainer:BROADCOM STB AVS CPUFREQ DRIVER"
	<bcm-kernel-feedback-list@broadcom.com>,
	Markus Mayer <mmayer@broadcom.com>,
	Brian Norris <computersforpeace@gmail.com>,
	"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes
Date: Mon, 27 May 2019 12:51:32 +0200	[thread overview]
Message-ID: <3734641.73qX0VsHyn@kreacher> (raw)
In-Reply-To: <20190522184547.31791-1-f.fainelli@gmail.com>

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.




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-05-27 10:51 UTC|newest]

Thread overview: 14+ 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 ` 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   ` Florian Fainelli
2019-05-22 18:45 ` [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: Fix types for voltage/frequency Florian Fainelli
2019-05-22 18:45   ` Florian Fainelli
2019-05-27 10:51 ` Rafael J. Wysocki [this message]
2019-05-27 10:51   ` [PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: Couple fixes Rafael J. Wysocki
2019-05-29 17:01   ` Florian Fainelli
2019-05-29 17:01     ` Florian Fainelli
2019-06-03 19:55     ` Markus Mayer
2019-06-03 19:55       ` Markus Mayer
2019-06-04  4:03       ` Viresh Kumar
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=3734641.73qX0VsHyn@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=f.fainelli@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.