From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: "Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Adam Ford" <aford173@gmail.com>,
"Andreas Kemnade" <andreas@kemnade.info>,
"Andrew Davis" <afd@ti.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Carl Philipp Klemm" <philipp@uvos.xyz>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Jarkko Nikula" <jarkko.nikula@bitmer.com>,
"Janusz Krzysztofik" <jmkrzyszt@gmail.com>,
Keerthy <j-keerthy@ti.com>, "Kevin Hilman" <khilman@baylibre.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Merlijn Wajer" <merlijn@wizzup.org>,
"Nishanth Menon" <nm@ti.com>, "Olof Johansson" <olof@lixom.net>,
"Paul Walmsley" <paul@pwsan.com>,
"Peter Ujfalusi" <peter.ujfalusi@gmail.com>,
"Praneeth Bajjuri" <praneeth@ti.com>,
"Roger Quadros" <rogerq@kernel.org>,
"Russell King" <linux@armlinux.org.uk>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
"Sicelo A. Mhlongo" <absicsz@gmail.com>,
"Tero Kristo" <kristo@kernel.org>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Vignesh R" <vigneshr@ti.com>
Subject: Adding more mach-omap2 maintainers
Date: Fri, 19 Apr 2024 08:52:49 +0300 [thread overview]
Message-ID: <20240419055249.GE5156@atomide.com> (raw)
Hi all,
I want to add some more maintainers for omaps to ensure continued support.
There are many generations of omaps, and having multiple maintainers allows
us to split the work. The earlier split by category to things like PM,
clocks, and SoC core interconnect hwmod/ti-sysc no longer exactly current
as the work has been completed, and people have moved on.
TI is naturally mainly interested in their active parts am3, am4 and dra7.
Additionally, the community folks are interested in maintaining also some
of the older devices, mostly based on omap3 and omap4.
So I'd like to add two maintainers from TI, and two community maintainers.
This allows both the TI and community maintainers take turns with the
merge windows and chasing down regressions.
I've started working full time at Intel and will be stepping back. I'll
be still around here and there too as a hobbyist maintainer tinkering
with some mobile devices I use :)
Over the past week, I've privately asked some folks who I trust to help.
I started with people who have been active recently related to omap
touching SoC devices.
From folks working on TI SoCs, I'd like to have Andrew Davis and
Roger Quardos to join. They both have a long history on working on omap
based devices, and are actively working on the SoC devices that are used
both for omaps and the new K3 SoCs. Kevin Hilman might be also able to
help a bit on some related Linux generic issues.
From the community side, I'd like to have Aaro Koskinen and Andreas Kemnade
to join. Both Aaro and Andreas have been working on multiple mainline
supported omap devices such as n900 and gta04.
I'd assume we get the final list sorted out over next week or so and then
I'll send a patch for the MAINTAINERS file. I've tried to Cc a bunch of
folks who have been involved, but probably missed lots of folks who have
been involved, so please add to Cc as needed.
Regards,
Tony
next reply other threads:[~2024-04-19 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 5:52 Tony Lindgren [this message]
2024-04-19 9:30 ` Adding more mach-omap2 maintainers Adam Ford
2024-06-05 16:20 ` Kevin Hilman
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=20240419055249.GE5156@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=absicsz@gmail.com \
--cc=afd@ti.com \
--cc=aford173@gmail.com \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=j-keerthy@ti.com \
--cc=jarkko.nikula@bitmer.com \
--cc=jmkrzyszt@gmail.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=merlijn@wizzup.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=paul@pwsan.com \
--cc=peter.ujfalusi@gmail.com \
--cc=philipp@uvos.xyz \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tomi.valkeinen@ideasonboard.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).