Re: [PATCH v2] MAINTAINERS: cpufreq: add bmips-cpufreq.c
From: Markus Mayer
Date: Sun Feb 19 2017 - 23:12:20 EST
On 19 February 2017 at 19:29, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> On 17-02-17, 12:27, Markus Mayer wrote:
>> From: Markus Mayer <mmayer@xxxxxxxxxxxx>
>> Add maintainer information for bmips-cpufreq.c.
>> Signed-off-by: Markus Mayer <mmayer@xxxxxxxxxxxx>
>> Acked-by: Florian Fainelli <f.fainelli@xxxxxxxxx>
>> 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 ) or it can remain separate.
>>  https://lkml.org/lkml/2017/2/7/775
>> Changes in v2:
>> - added bcm-kernel-feedback-list@xxxxxxxxxxxx
>> 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@xxxxxxxxxxxx>
>> +M: bcm-kernel-feedback-list@xxxxxxxxxxxx
> Isn't this a list as well? Shouldn't this be L: ?
We used to do that, but then there was a discussion at some point in
the past (I don't have the link handy for it at this point), where it
was suggested that we use M: for the Broadcom list, because it is a
private, closed list (i.e. you can't just go and subscribe). It does
reach a bunch of folks at Broadcom, however, who work on upstreaming.
Therefore, the reasoning was that it fits the "maintainer" category
better than the "list" category (where people might expect to be able
to subscribe or find a public archive).
>> +L: linux-pm@xxxxxxxxxxxxxxx
>> +S: Maintained
>> +F: drivers/cpufreq/bmips-cpufreq.c
>> BROADCOM TG3 GIGABIT ETHERNET DRIVER
>> M: Siva Reddy Kallam <siva.kallam@xxxxxxxxxxxx>
>> M: Prashant Sreedharan <prashant@xxxxxxxxxxxx>