From: Kevin Hilman <khilman@baylibre.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Roger Quadros <rogerq@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Nishanth Menon <nm@ti.com>, Olof Johansson <olof@lixom.net>,
Russell King <linux@armlinux.org.uk>, Vignesh R <vigneshr@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] MAINTAINERS: Add more maintainers for omaps
Date: Tue, 09 Jul 2024 07:57:20 -0700 [thread overview]
Message-ID: <7hmsmq7gvj.fsf@baylibre.com> (raw)
In-Reply-To: <20240709135930.3405-1-tony@atomide.com>
Tony Lindgren <tony@atomide.com> writes:
> There are many generations of omaps to maintain, and I will be only active
> as a hobbyist with time permitting. Let's add more maintainers to ensure
> continued Linux support.
>
> TI is interested in maintaining the active SoCs such as am3, am4 and
> dra7. And the hobbyists are interested in maintaining some of the older
> devices, mainly based on omap3 and 4 SoCs.
>
> Kevin and Roger have agreed to maintain the active TI parts. Both Kevin
> and Roger have been working on the omap variants for a long time, and
> have a good understanding of the hardware.
>
> Aaro and Andreas have agreed to maintain the community devices. Both Aaro
> and Andreas have long experience on working with the earlier TI SoCs.
>
> While at it, let's also change me to be a reviewer for the omap1, and
> drop the link to my old omap web page.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
Acked-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2024-07-09 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 13:59 [PATCH] MAINTAINERS: Add more maintainers for omaps Tony Lindgren
2024-07-09 14:57 ` Kevin Hilman [this message]
2024-07-09 16:31 ` Aaro Koskinen
2024-07-10 9:09 ` Roger Quadros
2024-07-11 6:44 ` Andreas Kemnade
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=7hmsmq7gvj.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.