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] MAINTAINERS: cpufreq: add bmips-cpufreq.c
Date: Fri, 17 Feb 2017 11:24:56 -0800 [thread overview]
Message-ID: <c7a1f607-6619-445a-db35-902f11569dad@gmail.com> (raw)
In-Reply-To: <20170217183050.31889-1-code@mmayer.net>
On 02/17/2017 10:30 AM, Markus Mayer wrote:
> From: Markus Mayer <mmayer@broadcom.com>
>
> Add maintainer information for bmips-cpufreq.c.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
Looks great, thanks for adding this, one nit below:
> ---
>
> This is based on PM's linux-next from today (February 17).
>
> This patch could be squashed into patch 3/4 of the original series if that
> is acceptable (see [1]) or it can remain separate.
>
> [1] https://lkml.org/lkml/2017/2/7/775
>
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 107c10e..db251c0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2692,6 +2692,12 @@ F: drivers/irqchip/irq-brcmstb*
> F: include/linux/bcm963xx_nvram.h
> F: include/linux/bcm963xx_tag.h
>
> +BROADCOM BMIPS CPUFREQ DRIVER
> +M: Markus Mayer <mmayer@broadcom.com>
> +L: linux-pm@vger.kernel.org
Please also include bcm-kernel-feedback-list@broadcom.com here
With that:
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2017-02-17 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 18:30 [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c Markus Mayer
2017-02-17 19:24 ` Florian Fainelli [this message]
2017-02-18 1:20 ` Rafael J. Wysocki
2017-02-18 1:26 ` Florian Fainelli
2017-02-18 1:37 ` Rafael J. Wysocki
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=c7a1f607-6619-445a-db35-902f11569dad@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