linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	"'Sam Protsenko'" <semen.protsenko@linaro.org>
Cc: "'Peter Griffin'" <peter.griffin@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"'Chanwoo	Choi'" <cw00.choi@samsung.com>,
	"'Marek Szyprowski'" <m.szyprowski@samsung.com>,
	"'Peter Griffin'" <peter.griffin@linaro.org>,
	"'Jaewon Kim'" <jaewon02.kim@samsung.com>,
	"'Mateusz Majewski'" <m.majewski2@samsung.com>,
	"'Henrik Grimler'" <henrik@grimler.se>,
	"'David Virag'" <virag.david003@gmail.com>,
	"'Artur Weber'" <aweber.kernel@gmail.com>,
	"'Raymond Hackley'" <raymondhackley@protonmail.com>
Subject: RE: [PATCH] MAINTAINERS: Add entry for Samsung Exynos850 SoC
Date: Fri, 26 Jul 2024 21:38:24 +0530	[thread overview]
Message-ID: <00de01dadf76$0d25ffa0$2771fee0$@samsung.com> (raw)
In-Reply-To: <ae202942-fdc0-4913-bd37-c167440807af@linaro.org>



> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: Friday, July 26, 2024 8:47 PM
> To: Sam Protsenko <semen.protsenko@linaro.org>
> Cc: Alim Akhtar <alim.akhtar@samsung.com>; Peter Griffin
> <peter.griffin@linaro.org>; linux-arm-kernel@lists.infradead.org; linux-
> samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org; Chanwoo Choi
> <cw00.choi@samsung.com>; Marek Szyprowski
> <m.szyprowski@samsung.com>; Peter Griffin <peter.griffin@linaro.org>;
> Jaewon Kim <jaewon02.kim@samsung.com>; Mateusz Majewski
> <m.majewski2@samsung.com>; Henrik Grimler <henrik@grimler.se>; David
> Virag <virag.david003@gmail.com>; Artur Weber <aweber.kernel@gmail.com>;
> Raymond Hackley <raymondhackley@protonmail.com>
> Subject: Re: [PATCH] MAINTAINERS: Add entry for Samsung Exynos850 SoC
> 
> On 30/01/2024 08:29, Krzysztof Kozlowski wrote:
> > On 29/01/2024 21:47, Sam Protsenko wrote:
> >> Add maintainers entry for the Samsung Exynos850 SoC based platforms.
> >>
> >> Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
> >> ---
> >>  MAINTAINERS | 10 ++++++++++
> >>  1 file changed, 10 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS index
> >> 939f6dd0ef6a..77c10cc669f8 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -19281,6 +19281,16 @@ B:	mailto:linux-samsung-
> soc@vger.kernel.org
> >>  F:	Documentation/devicetree/bindings/sound/samsung*
> >>  F:	sound/soc/samsung/
> >>
> >> +SAMSUNG EXYNOS850 SoC SUPPORT
> >> +M:	Sam Protsenko <semen.protsenko@linaro.org>
> >> +L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> >> +L:	linux-samsung-soc@vger.kernel.org
> >
> > Sorry, but I am still against individual SoC entries in maintainers,
> > like I replied multiple times and pointed to the updated
> > get_maintainers.pl script to fetch emails from boards.
> 
> I retract my earlier statement.
> 
> Some background: I was really hoping that scripts/get_maintainers.pl patch,
> which adds fetching emails from files (e.g. DTS), will be picked up, but it has
> been few years, few resends and there is no conclusion. I don't think it will be
> ever merged, thus this email.
> 
> Since C files do not have in-file "maintainer" entry and particular drivers have
> MAINTAINERS-file entries, then why DTS should be different?
> 
Not sure what was the discussion in past, do you think this need some discussion in LPC? 

> I'll take the patch after merge window.
> 
> +Cc few other folks,
> 
> I understand that with lei/lore filters one can easily track patches sent for
> particular boards or SoCs, but being listed in MAINTAINERS have a bit bigger
> meaning. Therefore if any of you consider / want to add themself to
> MAINTAINERS for particular DTS, then go ahead. By DTS I
> mean: particular boards (e.g. Galaxy Tab 3 family) or particular SoC (e.g.
> Exynos850 like here).
> 
Actually it is being confusing. Completely agreed that  "MAINTAINERS have a bit bigger".
By adding each DTS/SoC/Board MAINTAINERS entry, are those members expected to send pull requests?
If so, that leads to more confusion and overhead. 


> Best regards,
> Krzysztof




  reply	other threads:[~2024-07-26 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 20:47 [PATCH] MAINTAINERS: Add entry for Samsung Exynos850 SoC Sam Protsenko
2024-01-30  7:29 ` Krzysztof Kozlowski
2024-07-26 15:17   ` Krzysztof Kozlowski
2024-07-26 16:08     ` Alim Akhtar [this message]
2024-07-29  6:27       ` Krzysztof Kozlowski
2024-07-31 18:28     ` Sam Protsenko
2024-08-04 15:01 ` 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='00de01dadf76$0d25ffa0$2771fee0$@samsung.com' \
    --to=alim.akhtar@samsung.com \
    --cc=aweber.kernel@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=henrik@grimler.se \
    --cc=jaewon02.kim@samsung.com \
    --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=m.majewski2@samsung.com \
    --cc=m.szyprowski@samsung.com \
    --cc=peter.griffin@linaro.org \
    --cc=raymondhackley@protonmail.com \
    --cc=semen.protsenko@linaro.org \
    --cc=virag.david003@gmail.com \
    /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).