[PATCH 0/2] Regarding NAND core and drivers maintenance

[Brian Norris]

On Wed, Nov 20, 2013 at 09:20:07AM -0300, Ezequiel Garcia wrote:
> As it's obvious from the mailing list activity, in the past months Brian
> Norris took the NAND maintainership role. In my opinion, he's been doing
> a terrific work and as a result the reviewing cycle is now considerably
> shorter.
> 
> Great work, Brian!

Thanks!

> This position is not at all easy, due to each NAND driver being filled
> with hardware controller specificities. For that reason, I think it
> would be healthy to take another step in setting maintainership
> responsabilites.
> 
> My proposal (copy-pasted from the media subsystem) is to define
> sub-maintainers, one for each NAND driver, in addition to the top-level
> NAND subsystem maintainer.

I believe the offering is open, for any who are in a situation to
maintain particular drivers. You may note that there are a few NAND
drivers which are listed as "maintained" by others, either under their
corresponding ARM architecture, or standalone. And as you mention, this
arrangement is common in some other subsystems.

I don't suppose that every NAND driver will need a dedicated maintainer,
but active ones which have interested, knowledgeable developers might be
good candidates.

> When a patch comes for a given driver, the _ideal_ situation would be
> for the sub-maintainer to Ack-it first.
> 
> And to formalize this proposal, I'm pushing a couple patches: the first
> adds Brian to MAINTAINERS, as the NAND maintainer.
> 
> Then, I'm adding myself as sub-maintainer to the pxa3xx-nand driver.
> This way, scripts/get_maintainers.pl will show my mail and I'll get
> CCed by occasional or new contributors.
> 
> How does this sound?

For the idea:

Acked-by: Brian Norris <computersforpeace at gmail.com>

I think patch 1 would need a little tweaking, though.

I'd also like David's or Artem's comments. I know that Artem, for one,
claimed to not want to put himself in an official role as MTD
maintainer, even though he was taking much of this responsibility
previously.

Brian