[PATCH] ARM: Assume maintainership of ARM reference designs

Arnd Bergmann arnd at arndb.de
Fri Sep 28 02:12:05 PDT 2018


On Fri, Sep 28, 2018 at 10:46 AM Linus Walleij <linus.walleij at linaro.org> wrote:
>
> On Fri, Sep 28, 2018 at 9:45 AM Arnd Bergmann <arnd at arndb.de> wrote:
> > On Fri, Sep 28, 2018 at 12:04 AM Mark Brown <broonie at kernel.org> wrote:
> > > On Thu, Sep 27, 2018 at 09:37:33AM +0200, Linus Walleij wrote:
> > >
> > > > +F:   drivers/spi/spi-pl022.c
> > >
> > > The pl022 is actively used by *way* more than just the Arm reference
> > > platforms, it's a really popular IP though the driver is fairly feature
> > > complete at this point.  I'd like to at least see this split out as a
> > > separate thing rather than lumped in so that people don't discount the
> > > get_maintainers match as a false positive, though I'm totally fine with
> > > you taking it over.
> >
> > The same logic probably applies to irq-vic.c, which is used on at least
> > five other platforms.
>
> I just saw that they were all orphaned so vaccumed them up from
> the floor.
>
> They are ARM PrimeCells that originate in these reference
> designs: the VHDL code is on the CD that comes with Integrator,
> Versatile etc, that is why this is appearing in more places,
> companies bought the reference designs and took the VHDL
> off the CD and started working on their SoC. So in some esoteric
> sense they are closest associated with the reference designs.
>
> So should I split out the SPI PL022 and VIC PL190 into their
> own MAINTAINERS entries, simply?

Yes, please do.

      Arnd



More information about the linux-arm-kernel mailing list