[PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.
f.fainelli at gmail.com
Tue Jan 31 12:55:26 PST 2017
On 01/31/2017 12:32 PM, Michael Zoran wrote:
> On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote:
>> I've been maintaining the bcm2835 branches here for a year or so.
>> Signed-off-by: Eric Anholt <eric at anholt.net>
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 844835563ef8..64b281a7ff09 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2624,7 +2624,7 @@ M: Lee Jones <lee at kernel.org>
>> M: Eric Anholt <eric at anholt.net>
>> L: linux-rpi-kernel at lists.infradead.org (moderated for non-
>> L: linux-arm-kernel at lists.infradead.org (moderated for non-
>> -T: git
>> +T: git git://github.com/anholt/linux
>> S: Maintained
>> N: bcm283[5-7x]
>> F: drivers/staging/vc04_services
> Just to add two cents here, since this is sort of a open source
> community driven thing, I think there should be multiple maintainers in
> case of a disagreement. 2 is good, 3 is better so that it's impossible
> to have a split disagreement and the third person can break the tie.
You may want to look at the file, and not the diff, which is already
listing 3 people.
> Github is cool as the e-mail based system is really, really bad. But
> if it is on github, I think it should have a neutral name not a
> person's name and allow multiple people to merge in pulls.
> Unless of course, Eric wants to take 100% control of this whole thing.
Really not clear what point you are trying to make here, other than you
may not like how things are, but at some point, someone needs to merge
patches somewhere, in a repository that's convenient, only to have them
pulled by whoever is next up in the food chain. Where the code is really
does not matter much because: git is distributed, patches can be
collected from mailing-list archives.
More information about the linux-rpi-kernel