From: Florian Fainelli <f.fainelli@gmail.com>
To: Markus Mayer <code@mmayer.net>,
Ralf Baechle <ralf@linux-mips.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: Markus Mayer <mmayer@broadcom.com>,
MIPS Linux Kernel List <linux-mips@linux-mips.org>,
Power Management List <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] cpufreq: bmips-cpufreq: CPUfreq driver for Broadcom's BMIPS SoCs
Date: Tue, 7 Feb 2017 18:07:22 -0800 [thread overview]
Message-ID: <ffce8d46-0f9c-5145-82ef-a62920b55f0e@gmail.com> (raw)
In-Reply-To: <20170207215856.8999-4-code@mmayer.net>
On 02/07/2017 01:58 PM, Markus Mayer wrote:
> From: Markus Mayer <mmayer@broadcom.com>
>
> Add the MIPS CPUfreq driver. This driver currently supports CPUfreq on
> BMIPS5xxx-based SoCs.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2017-02-08 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 21:58 [PATCH v3 0/4] cpufreq: bmips-cpufreq: Add CPUfreq driver for Broadcom's BMIPS SoCs Markus Mayer
2017-02-07 21:58 ` [PATCH v3 1/4] MIPS: BMIPS: Update defconfig Markus Mayer
2017-02-07 21:58 ` [PATCH v3 2/4] BMIPS: Enable prerequisites for CPUfreq in MIPS Kconfig Markus Mayer
2017-02-08 2:07 ` Florian Fainelli
2017-02-07 21:58 ` [PATCH v3 3/4] cpufreq: bmips-cpufreq: CPUfreq driver for Broadcom's BMIPS SoCs Markus Mayer
2017-02-08 2:07 ` Florian Fainelli [this message]
2017-02-08 3:31 ` Viresh Kumar
2017-02-07 21:58 ` [PATCH v3 4/4] MIPS: BMIPS: enable CPUfreq Markus Mayer
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=ffce8d46-0f9c-5145-82ef-a62920b55f0e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=code@mmayer.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=ralf@linux-mips.org \
--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).