From: "André Draszik" <andre.draszik@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: samsung: MAINTAINERS: Add Tesla FSD DTS to Exynos entry
Date: Thu, 10 Jul 2025 08:41:07 +0100 [thread overview]
Message-ID: <fe445967514bbbb5bbbcc806f98dd6bbac9e032a.camel@linaro.org> (raw)
In-Reply-To: <20250710073443.13788-4-krzysztof.kozlowski@linaro.org>
On Thu, 2025-07-10 at 09:34 +0200, Krzysztof Kozlowski wrote:
> Effectively all Tesla FSD DTS patches go via Samsung Exynos SoC
> maintainer, so add the pattern to make it obvious and reduce the chances
> patches won't reach these maintainers.
>
> Cc: Peter Griffin <peter.griffin@linaro.org>
> Cc: André Draszik <andre.draszik@linaro.org>
> Cc: Tudor Ambarus <tudor.ambarus@linaro.org>
> Cc: Alim Akhtar <alim.akhtar@samsung.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: André Draszik <andre.draszik@linaro.org>
next prev parent reply other threads:[~2025-07-10 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250710073503epcas5p2ad88e48f23891c3592522dd22aee7bf9@epcas5p2.samsung.com>
2025-07-10 7:34 ` [PATCH 1/2] arm64: tesla/google: MAINTAINERS: Reference "SoC clean" maintainer profile Krzysztof Kozlowski
2025-07-10 7:34 ` [PATCH 2/2] arm64: samsung: MAINTAINERS: Add Tesla FSD DTS to Exynos entry Krzysztof Kozlowski
2025-07-10 7:41 ` André Draszik [this message]
2025-07-10 8:12 ` Alim Akhtar
2025-07-10 7:40 ` [PATCH 1/2] arm64: tesla/google: MAINTAINERS: Reference "SoC clean" maintainer profile André Draszik
2025-07-10 8:00 ` Peter Griffin
2025-07-10 8:11 ` Alim Akhtar
2025-07-15 9:07 ` 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=fe445967514bbbb5bbbcc806f98dd6bbac9e032a.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.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;
as well as URLs for NNTP newsgroup(s).