From: Markus Mayer <code@mmayer.net>
To: 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: [PATCH v2] MAINTAINERS: cpufreq: add bmips-cpufreq.c
Date: Fri, 17 Feb 2017 12:27:03 -0800 [thread overview]
Message-ID: <20170217202704.33596-1-code@mmayer.net> (raw)
From: Markus Mayer <mmayer@broadcom.com>
Add maintainer information for bmips-cpufreq.c.
Signed-off-by: Markus Mayer <mmayer@broadcom.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
---
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
Changes in v2:
- added bcm-kernel-feedback-list@broadcom.com
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 107c10e..d4ac248 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2692,6 +2692,13 @@ 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>
+M: bcm-kernel-feedback-list@broadcom.com
+L: linux-pm@vger.kernel.org
+S: Maintained
+F: drivers/cpufreq/bmips-cpufreq.c
+
BROADCOM TG3 GIGABIT ETHERNET DRIVER
M: Siva Reddy Kallam <siva.kallam@broadcom.com>
M: Prashant Sreedharan <prashant@broadcom.com>
--
2.7.4
next reply other threads:[~2017-02-17 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 20:27 Markus Mayer [this message]
2017-02-20 3:29 ` [PATCH v2] MAINTAINERS: cpufreq: add bmips-cpufreq.c Viresh Kumar
2017-02-20 4:10 ` 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=20170217202704.33596-1-code@mmayer.net \
--to=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