From: Chanwoo Choi <cw00.choi@samsung.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: tomasz.figa@gmail.com, k.kozlowski@samsung.com, kgene@kernel.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, chanwoo@kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add myself as SAMSUNG SOC CLOCK DRIVERS
Date: Mon, 22 Aug 2016 19:19:45 +0900 [thread overview]
Message-ID: <57BAD1C1.9070306@samsung.com> (raw)
In-Reply-To: <76aea8a8-cda7-ca9f-54ff-d614d834dde0@samsung.com>
Hi Sylwester,
On 2016년 08월 22일 19:01, Sylwester Nawrocki wrote:
> Hi Chanwoo,
>
> On 08/18/2016 02:47 PM, Chanwoo Choi wrote:
>> Add the myself to the entry of SAMSUNG SOC CLOCK DRIVERS to review
>> and test the patches as supporter. I will help them. I can access the all
>> datasheet of Exynos SoC and test it on Exynos-based board. I was implemented
>> the exynos4415/5433 clock driver as author and handled the exynos3250 clock
>> driver. Lastly, adding the missing information of the exynos clock drivers.
>>
>> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> Cc: Tomasz Figa <tomasz.figa@gmail.com>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>
> I'm going to apply this patch with commit message rephrased as below.
>
> "MAINTAINERS: Add myself as SAMSUNG SOC CLOCK DRIVERS co-maintainer
>
> Add myself to the SAMSUNG SOC CLOCK DRIVERS entry, I'm going to review
> and test related patches as supporter. I can access all the datasheet
> of Exynos SoC series and can do tests on Exynos based boards. I have
> implemented the exynos4415/5433 clock drivers and co-authored the
> exynos3250 clock driver. While at it, add missing paths of the exynos
> clock driver files."
>
> Please let me know if you see any issues with that.
There is no issue. Thanks.
Best Regards,
Chanwoo Choi
>
>> ---
>> MAINTAINERS | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 20bb1d00098c..442d6f5c65be 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10233,9 +10233,12 @@ F: drivers/nfc/s3fwrn5
>> SAMSUNG SOC CLOCK DRIVERS
>> M: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> M: Tomasz Figa <tomasz.figa@gmail.com>
>> +M: Chanwoo Choi <cw00.choi@samsung.com>
>> S: Supported
>> L: linux-samsung-soc@vger.kernel.org (moderated for non-subscribers)
>> F: drivers/clk/samsung/
>> +F: include/dt-bindings/clock/exynos*.h
>> +F: Documentation/devicetree/bindings/clock/exynos*.txt
>>
>> SAMSUNG SXGBE DRIVERS
>> M: Byungho An <bh74.an@samsung.com>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-clk" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2016-08-22 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 12:47 [PATCH] MAINTAINERS: Add myself as SAMSUNG SOC CLOCK DRIVERS Chanwoo Choi
2016-08-22 10:01 ` Sylwester Nawrocki
2016-08-22 10:19 ` Chanwoo Choi [this message]
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=57BAD1C1.9070306@samsung.com \
--to=cw00.choi@samsung.com \
--cc=chanwoo@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@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