From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Alim Akhtar" <alim.akhtar@samsung.com>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Peter Griffin" <peter.griffin@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linusw@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] MAINTAINERS: Add myself as a co-maintainer of Samsung Exynos SoCs
Date: Sat, 30 May 2026 18:34:40 +0200 [thread overview]
Message-ID: <178015858043.36212.8088079079471293822.b4-ty@b4> (raw)
In-Reply-To: <20260527-samsung-soc-maintainer-v1-1-40829c3fb133@linaro.org>
On Wed, 27 May 2026 21:24:29 +0100, Peter Griffin wrote:
> As Google Tensor gs101 is based off a Samsung Exynos design I've been
> working on many of these drivers and have an interest in helping maintain
> this code.
I have multiple subsystems to care of and limited time. Also, with joining to
SoC team I figured out it is good to plan my succession. Or backup.
Peter shown both time and interest in keeping Samsung Exynos code working, thus
considering above, I proposed Peter to become a co-maintainer here (same for
pinctrl, which went via different tree).
I will still be the one handling patches for this and (probably) next cycle,
but in a further timeframe the roles could reverse with me only providing acks
or reviews. If this works then depending on other duties and amount of work, I
might be slowly transitioning to leave Samsung SoC maintainership.
Applied, thanks!
[1/1] MAINTAINERS: Add myself as a co-maintainer of Samsung Exynos SoCs
https://git.kernel.org/krzk/linux/c/20550601bf4c23effa013a5f37e5250618869e87
Best regards,
--
Krzysztof Kozlowski <krzk@kernel.org>
prev parent reply other threads:[~2026-05-30 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 20:24 [PATCH] MAINTAINERS: Add myself as a co-maintainer of Samsung Exynos SoCs Peter Griffin
2026-05-30 16:34 ` Krzysztof Kozlowski [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=178015858043.36212.8088079079471293822.b4-ty@b4 \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=arnd@arndb.de \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.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