From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
krzk@kernel.org, javier@osg.samsung.com, kgene@kernel.org,
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 18:59:52 +0200 [thread overview]
Message-ID: <20170105165952.yj5m4cm7zejvnayx@kozik-lap> (raw)
In-Reply-To: <20170105134104.zzjdirdiuqj6efyy@gangnam.samsung>
On Thu, Jan 05, 2017 at 10:41:04PM +0900, Andi Shyti wrote:
> Hi Daniel,
>
> > > +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*
> > > +
> >
> > Does it make sense to add a MAINTAINER entry for some dts files ?
>
> I think it does considering that exynos5433* files are more then
> the half of the arm64/.../exynos/ directory.
>
> Besides Chanwoo has authored all of them (almost) and doesn't
> appear from the get_maintainers script.
He appears:
1. Kukjin Kim <kgene@kernel.org> (maintainer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES)
2. Krzysztof Kozlowski <krzk@kernel.org> (maintainer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES,commit_signer:26/24=100%,authored:4/24=17%)
3. Javier Martinez Canillas <javier@osg.samsung.com> (reviewer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES,commit_signer:6/24=25%)
4. Marek Szyprowski <m.szyprowski@samsung.com> (commit_signer:12/24=50%,authored:8/24=33%)
5. Chanwoo Choi <cw00.choi@samsung.com> (commit_signer:9/24=38%,authored:3/24=12%)
6. Sylwester Nawrocki <s.nawrocki@samsung.com> (commit_signer:9/24=38%)
(sorry if lines are wrapped)
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-01-05 17:00 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
[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 [this message]
2017-01-06 3:21 ` Chanwoo Choi
2017-01-06 6:15 ` Krzysztof Kozlowski
2017-01-05 13:36 ` Javier Martinez Canillas
2017-01-05 13:47 ` Chanwoo Choi
2017-01-05 17:09 ` Krzysztof Kozlowski
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=20170105165952.yj5m4cm7zejvnayx@kozik-lap \
--to=krzk@kernel.org \
--cc=andi.shyti@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=daniel.lezcano@linaro.org \
--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®