From: Chanwoo Choi <cw00.choi@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Andi Shyti <andi.shyti@samsung.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.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: Fri, 06 Jan 2017 12:21:44 +0900 [thread overview]
Message-ID: <586F0D48.9050104@samsung.com> (raw)
In-Reply-To: <20170105165952.yj5m4cm7zejvnayx@kozik-lap>
[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]
On 2017년 01월 06일 01:59, Krzysztof Kozlowski wrote:
> 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)
I have a question.
When I tested the get_maintainer script with Exynos5444 patch,
I cannot get the same result from you.
I tested the following patch[1] which was already merged by Marek.
[1] commit-id: 74c78036d5b5970266fa2075a17c9b89cabf873e
- ("arm64: dts: exynos: TM2 - add support for MFC video codec device"
./scripts/get_maintainer.pl 0001-arm64-dts-exynos-TM2-add-support-for-MFC-video-codec.patch
Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
Mark Rutland <mark.rutland@arm.com> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
Catalin Marinas <catalin.marinas@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
Will Deacon <will.deacon@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
Kukjin Kim <kgene@kernel.org> (maintainer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES)
Krzysztof Kozlowski <krzk@kernel.org> (maintainer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES)
Javier Martinez Canillas <javier@osg.samsung.com> (reviewer:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES)
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
linux-arm-kernel@lists.infradead.org (moderated list:ARM64 PORT (AARCH64 ARCHITECTURE))
linux-samsung-soc@vger.kernel.org (moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES)
linux-kernel@vger.kernel.org (open list)
Also, when I tested the exynos5433-tm2e.dts patch, I got the same result.
>
> Best regards,
> Krzysztof
>
>
>
--
Best Regards,
Chanwoo Choi
Samsung Electronics
[-- Attachment #2: cw00_choi.vcf --]
[-- Type: text/x-vcard, Size: 6 bytes --]
null
next prev parent reply other threads:[~2017-01-06 3:22 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 ` [PATCH] MAINTAINERS: Add EXYNOS5433 ARM architectures entry as a supporter 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 [this message]
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=586F0D48.9050104@samsung.com \
--to=cw00.choi@samsung.com \
--cc=andi.shyti@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@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