From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Assume maintainership of ARM reference designs
Date: Fri, 28 Sep 2018 09:44:45 +0200 [thread overview]
Message-ID: <CAK8P3a21dCJuV7mmsVPboWXfxjEpBsiBh37nCk5WGRXWaMUHMg@mail.gmail.com> (raw)
In-Reply-To: <20180927220439.GB20825@sirena.org.uk>
On Fri, Sep 28, 2018 at 12:04 AM Mark Brown <broonie@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.
Arnd
next prev parent reply other threads:[~2018-09-28 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 7:37 [PATCH] ARM: Assume maintainership of ARM reference designs Linus Walleij
2018-09-27 8:25 ` Wolfram Sang
2018-09-27 8:26 ` Wolfram Sang
2018-09-27 18:49 ` Olof Johansson
2018-09-27 22:04 ` Mark Brown
2018-09-28 7:44 ` Arnd Bergmann [this message]
2018-09-28 8:46 ` Linus Walleij
2018-09-28 9:12 ` Arnd Bergmann
2018-09-27 22:55 ` Michael Turquette
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 13:14 Linus Walleij
2018-04-12 13:17 ` Russell King - ARM Linux
2018-04-12 13:18 ` Russell King - ARM Linux
2018-04-12 13:44 ` Linus Walleij
2018-04-12 13:52 ` Russell King - ARM Linux
2018-04-12 13:59 ` Linus Walleij
2018-04-12 14:02 ` Russell King - ARM Linux
2018-04-12 14:19 ` Sudeep Holla
2018-04-12 13:22 ` Wolfram Sang
2018-04-12 13:31 ` Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK8P3a21dCJuV7mmsVPboWXfxjEpBsiBh37nCk5WGRXWaMUHMg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).