From: Kevin Hilman <khilman@kernel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Cc: nfraprado@collabora.com, wenst@chromium.org,
matthias.bgg@gmail.com, robh@kernel.org, amergnat@baylibre.com,
arnd@arndb.de,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer
Date: Wed, 04 Oct 2023 11:08:36 -0700 [thread overview]
Message-ID: <7h8r8i5kgr.fsf@baylibre.com> (raw)
In-Reply-To: <20230929082009.71843-1-angelogioacchino.delregno@collabora.com>
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com> writes:
> I am a top reviewer mainly for MediaTek SoC related patches in most
> subsystems and I've also been upstreaming both improvements, fixes
> and new drivers and devicetrees when required.
>
> The MediaTek scene saw a generous increase in number of patches that
> are sent to the lists every week, increasing the amount of required
> efforts to maintain the MTK bits overall, and we will possibly see
> even more of that.
>
> For this reason, and also because of suggestions and encouragement
> coming from the community, I'm stepping up to be a co-maintainer of
> MediaTek SoCs support.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Acked-by: Kevin Hilman <khilman@baylibre.com>
Thank you Matthias for all the work you've put in over the years to
maintain MTK SoCs, and thank you to Angelo for stepping up to help as
the volume of maintainer work is increasing.
Kevin
prev parent reply other threads:[~2023-10-04 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 8:20 [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer AngeloGioacchino Del Regno
2023-09-29 19:36 ` Arnd Bergmann
2023-10-02 3:30 ` Chen-Yu Tsai
2023-10-02 8:27 ` AngeloGioacchino Del Regno
2023-10-02 9:04 ` Chen-Yu Tsai
2023-09-30 7:55 ` Frank Wunderlich
2023-10-02 3:31 ` Chen-Yu Tsai
2023-10-02 9:41 ` Matthias Brugger
2023-10-02 10:20 ` AngeloGioacchino Del Regno
2023-10-04 12:18 ` Alexandre Mergnat
2023-10-02 10:23 ` Matthias Brugger
2023-10-04 18:08 ` Kevin Hilman [this message]
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=7h8r8i5kgr.fsf@baylibre.com \
--to=khilman@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=robh@kernel.org \
--cc=wenst@chromium.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).