From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Linus Walleij'" <linusw@kernel.org>
Cc: <krzk@kernel.org>, <peter.griffin@linaro.org>, <robh@kernel.org>,
<conor+dt@kernel.org>, <linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <hajun.sung@samsung.com>
Subject: RE: [PATCH 5/5] MAINTAINERS: Add entry for Samsung Exynos8855 SoC
Date: Mon, 15 Jun 2026 13:34:59 +0530 [thread overview]
Message-ID: <007a01dcfc9d$aa94dd60$ffbe9820$@samsung.com> (raw)
In-Reply-To: <CAD++jL=mQUJCqVyqK746UdkZCsO+2oeO1MCQM4F-_pSOfpuQuA@mail.gmail.com>
Thanks Linus for your review
> -----Original Message-----
> From: Linus Walleij <linusw@kernel.org>
> Sent: Monday, June 15, 2026 12:51 PM
> To: Alim Akhtar <alim.akhtar@samsung.com>
> Cc: krzk@kernel.org; peter.griffin@linaro.org; robh@kernel.org;
> conor+dt@kernel.org; linux-samsung-soc@vger.kernel.org; linux-
> kernel@vger.kernel.org; devicetree@vger.kernel.org; linux-
> gpio@vger.kernel.org; hajun.sung@samsung.com
> Subject: Re: [PATCH 5/5] MAINTAINERS: Add entry for Samsung Exynos8855
> SoC
>
> Hi Alim,
>
> On Fri, Jun 12, 2026 at 6:11 PM Alim Akhtar <alim.akhtar@samsung.com>
> wrote:
>
> > Add maintainers entry for the Samsung Exynos8855 SoC based platforms
> >
> > Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
> (...)
> > +SAMSUNG EXYNOS8855 SoC SUPPORT
> > +M: Alim Akhtar <alim.akhtar@samsung.com>
> > +L: linux-arm-kernel@lists.infradead.org (moderated for non-
> subscribers)
> > +L: linux-samsung-soc@vger.kernel.org
> > +S: Maintained
> > +F: arch/arm64/boot/dts/exynos/exynos8855*
>
> If you really want to single out a single platform like this (and I don't even
> know if that is a good idea... how do you keep the big picture in mind?) you
> should probably want to also add a wildcard for all the
> 8855 device tree files.
>
I am also not sure, just followed what was done historically, other Exynos8855 file will get added once they
are posted for review, e.g. clock driver.
Let me discuss with Krzk during OSS (Mumbai) and see how do we handle this or any other better ways.
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2026-06-15 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260612161128epcas5p2fe6ebf4b1a7b3ad1794804768180cbdd@epcas5p2.samsung.com>
2026-06-12 16:30 ` [PATCH 0/5] Add minimal Exynos8855 SoC support Alim Akhtar
2026-06-12 16:30 ` [PATCH 1/5] dt-binding: ARM: samsung: Add Samsung Exynos8855 Alim Akhtar
2026-06-12 16:30 ` [PATCH 2/5] dt-binding: pinctrl: samsung: Add exynos8855-pinctrl compatible Alim Akhtar
2026-06-12 16:30 ` [PATCH 3/5] pinctrl: samsung: Add Exynos8855 pinctrl configuration Alim Akhtar
2026-06-12 16:30 ` [PATCH 4/5] arm64: dts: exynos: add initial support for Samsung Exynos8855 smdk Alim Akhtar
2026-06-12 16:30 ` [PATCH 5/5] MAINTAINERS: Add entry for Samsung Exynos8855 SoC Alim Akhtar
2026-06-15 7:21 ` Linus Walleij
2026-06-15 8:04 ` Alim Akhtar [this message]
2026-06-15 8:12 ` Krzysztof Kozlowski
2026-06-15 8:16 ` Krzysztof Kozlowski
2026-06-15 8:37 ` Alim Akhtar
2026-06-15 12:39 ` Linus Walleij
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='007a01dcfc9d$aa94dd60$ffbe9820$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hajun.sung@samsung.com \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.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