From: "Sylwester Nawrocki" <s.nawrocki@samsung•com>
To: "'Peter Griffin'" <peter.griffin@linaro•org>,
"'Krzysztof Kozlowski'" <krzk@kernel•org>,
"'Alim Akhtar'" <alim.akhtar@samsung•com>,
"'Chanwoo Choi'" <cw00.choi@samsung•com>,
"'André Draszik'" <andre.draszik@linaro•org>,
"'Tudor Ambarus'" <tudor.ambarus@linaro•org>,
"'Stephen Boyd'" <sboyd@kernel•org>,
"'Michael Turquette'" <mturquette@baylibre•com>,
"'Brian Masney'" <bmasney@redhat•com>
Cc: <linux-kernel@vger•kernel.org>,
<linux-arm-kernel@lists•infradead.org>,
<linux-samsung-soc@vger•kernel.org>
Subject: RE: [PATCH] MAINTAINERS: add myself as a co-maintainer for Samsung SoC clock drivers
Date: Thu, 28 May 2026 10:46:20 +0200 [thread overview]
Message-ID: <001a01dcee7e$75221490$5f663db0$@samsung.com> (raw)
In-Reply-To: <20260527-samsung-clk-maintainer-v1-1-97b179224ca5@linaro.org>
> -----Original Message-----
> From: Peter Griffin <peter.griffin@linaro•org>
> Subject: [PATCH] MAINTAINERS: add myself as a co-maintainer for Samsung
> SoC clock drivers
>
> As Google Tensor gs101 is based off a Samsung Exynos design I've been
> working on the Samsung SoC clock drivers and have an interest in helping
> maintain this code in the kernel.
>
> Signed-off-by: Peter Griffin <peter.griffin@linaro•org>
> ---
> This follows discussions with Krzysztof about expanding the Samsung SoC
> maintenance team in the kernel.
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung•com>
next prev parent reply other threads:[~2026-05-28 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260527205405eucas1p15ef3a9c4021f760ababa4bfdde18251f@eucas1p1.samsung.com>
2026-05-27 20:53 ` [PATCH] MAINTAINERS: add myself as a co-maintainer for Samsung SoC clock drivers Peter Griffin
2026-05-28 8:46 ` Sylwester Nawrocki [this message]
2026-05-30 16:34 ` Krzysztof Kozlowski
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='001a01dcee7e$75221490$5f663db0$@samsung.com' \
--to=s.nawrocki@samsung$(echo .)com \
--cc=alim.akhtar@samsung$(echo .)com \
--cc=andre.draszik@linaro$(echo .)org \
--cc=bmasney@redhat$(echo .)com \
--cc=cw00.choi@samsung$(echo .)com \
--cc=krzk@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-samsung-soc@vger$(echo .)kernel.org \
--cc=mturquette@baylibre$(echo .)com \
--cc=peter.griffin@linaro$(echo .)org \
--cc=sboyd@kernel$(echo .)org \
--cc=tudor.ambarus@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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