From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: krzk@kernel.org, javier@osg.samsung.com, kgene@kernel.org,
andi.shyti@samsung.com, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add EXYNOS5433 ARM architectures entry as a supporter
Date: Thu, 5 Jan 2017 19:09:51 +0200 [thread overview]
Message-ID: <20170105170951.2yftdz4nfqsgauoc@kozik-lap> (raw)
In-Reply-To: <1483621969-27631-1-git-send-email-cw00.choi@samsung.com>
On Thu, Jan 05, 2017 at 10:12:49PM +0900, Chanwoo Choi wrote:
> This patch adds the 'ARM/SAMSUNG EXYNOS5433 ARM ARCHITECTURES' entry
> in order to review and test the upcoming patches as a supporter.
> I have developed the low-level devices and power related devices for
> Exyno5433 and TM2/E board.
>
> Moreover, Andi proposed himself as a reviewer for Exynos5433 and TM2/E.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
> ---
> MAINTAINERS | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cfff2c9e3d94..96c055e8dd0b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1712,6 +1712,13 @@ F: Documentation/devicetree/bindings/sram/samsung-sram.txt
> F: Documentation/devicetree/bindings/power/pd-samsung.txt
> N: exynos
>
> +ARM/SAMSUNG EXYNOS5433 ARM ARCHITECTURES
> +M: Chanwoo Choi <cw00.choi@samsung.com>
> +R: Andi Shyti <andi.shyti@samsung.com>
> +L: linux-samsung-soc@vger.kernel.org (moderated for non-subscribers)
> +S: Supported
> +F: arch/arm64/boot/dts/exynos/exynos5433*
> +
Review and testing is always highly appreciated and you are doing,
Chanwoo, great work. I would like to sincerely thank you for that.
Samsung probably should thank you, as well. :)
As for the additional sub-entry, I do not see any need for creating
such entries for specific DTSes. This looks like overkill.
At the same time I would like to strongly avoid something which is
happening for example in our DRM where we have *four* maintainers but
only *one* is responding. We can add bazilions of maintainers to satisfy
Samsung KPIs but still this might not help reviewing patches (damn, why
am I waiting with this small [0] thing since 21st of October?).
On the other hand, this is just my personal opinion. If the broad
open-source community would like to do any changes here
(add/remove/move/whatever) I do not mind at all.
Best regards and happy New Year! :D
Krzysztof
next prev parent reply other threads:[~2017-01-05 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170105131251epcas1p18bb302757d0e45145595cc68c4ad947e@epcas1p1.samsung.com>
2017-01-05 13:12 ` Chanwoo Choi
2017-01-05 13:36 ` Javier Martinez Canillas
2017-01-05 13:47 ` Chanwoo Choi
[not found] ` <43019997-a6cf-30df-2437-306055ea6a78@linaro.org>
2017-01-05 13:36 ` Chanwoo Choi
2017-01-05 13:41 ` Andi Shyti
2017-01-05 16:59 ` Krzysztof Kozlowski
2017-01-06 3:21 ` Chanwoo Choi
2017-01-06 6:15 ` Krzysztof Kozlowski
2017-01-05 17:09 ` Krzysztof Kozlowski [this message]
2017-01-05 17:19 ` Krzysztof Kozlowski
2017-01-06 3:15 ` Chanwoo Choi
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=20170105170951.2yftdz4nfqsgauoc@kozik-lap \
--to=krzk@kernel.org \
--cc=andi.shyti@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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
all inboxes | Powered by JetHome®