Skip to contentSkip to conversation

arm-soc maintainer entry

PATCH Stephen Boyd 2 participants 4 messages Oct 4, 2012

lore
Share & tools
lore
#0 lore raw

Is the arm at kernel.org alias going to be added into the MAINTAINERS file? Should anybody be sending mails to this address?

It seems I asked this over a year ago and the response was positive but nothing ever happened[1]. Maybe something like below? I only ask because get_maintainer.pl isn't picking up this email.

MAINTAINERS +8 -0
index ecd8796..0e1ec23 100644
@@ -606,6 +606,14 @@ W: http://www.arm.linux.org.uk/
 S:     Maintained
 F:     arch/arm/
 
+ARM SUB-ARCHITECTURES
+M:     arm at kernel.org
+L:     linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
+S:     MAINTAINED
+F:     arch/arm/mach-*/
+F:     arch/arm/plat-*/
+T:     git git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
+
 ARM PRIMECELL AACI PL041 DRIVER
 M:     Russell King <[email protected]>
 S:     Maintained

[1] https://lkml.org/lkml/2011/7/26/307

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#1 lore raw

Hi,

Quoted 6 lines · Stephen Boyd

Is the arm at kernel.org alias going to be added into the MAINTAINERS file? Should anybody be sending mails to this address?

It seems I asked this over a year ago and the response was positive but nothing ever happened[1]. Maybe something like below? I only ask because get_maintainer.pl isn't picking up this email.

I've been holding off re-proposing this, mostly because life is easier for us if we don't get arm at kernel.org cc:d on every single patch by people who run get_maintainers.pl -- it's the equivalent of getting linux-arm-kernel cc:d to your inbox. It's better signal-to-noise ratio if it's mostly platform maintainers that email us on that address with pull requests or patches they want applied.

But yeah, it also means that the maintainer structure is undocumented. I'm open for suggestions.

-Olof

#2 lore raw
Quoted 16 lines · Olof Johansson

Hi,

Quoted 6 lines · Stephen Boyd

Is the arm at kernel.org alias going to be added into the MAINTAINERS file? Should anybody be sending mails to this address?

It seems I asked this over a year ago and the response was positive but nothing ever happened[1]. Maybe something like below? I only ask because get_maintainer.pl isn't picking up this email.

I've been holding off re-proposing this, mostly because life is easier for us if we don't get arm at kernel.org cc:d on every single patch by people who run get_maintainers.pl -- it's the equivalent of getting linux-arm-kernel cc:d to your inbox. It's better signal-to-noise ratio if it's mostly platform maintainers that email us on that address with pull requests or patches they want applied.

Quoted 3 lines

But yeah, it also means that the maintainer structure is undocumented. I'm open for suggestions.

Thanks for clarifying. Maybe we can put in the git tree and no email address? That at least documents some structure.

Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
#3 lore raw
Quoted 17 lines · Stephen Boyd
Quoted 16 lines · Olof Johansson

Hi,

Quoted 6 lines · Stephen Boyd

Is the arm at kernel.org alias going to be added into the MAINTAINERS file? Should anybody be sending mails to this address?

It seems I asked this over a year ago and the response was positive but nothing ever happened[1]. Maybe something like below? I only ask because get_maintainer.pl isn't picking up this email.

I've been holding off re-proposing this, mostly because life is easier for us if we don't get arm at kernel.org cc:d on every single patch by people who run get_maintainers.pl -- it's the equivalent of getting linux-arm-kernel cc:d to your inbox. It's better signal-to-noise ratio if it's mostly platform maintainers that email us on that address with pull requests or patches they want applied.

Quoted 6 lines
Quoted 3 lines

But yeah, it also means that the maintainer structure is undocumented. I'm open for suggestions.

Thanks for clarifying. Maybe we can put in the git tree and no email address? That at least documents some structure.

Ah, yes, that makes a lot of sense.

-Olof